Skip to content
Campus Alert Archive
UH

Robbery, February 7, 2026

AI-generated · every claim is source-linked
TXrobberytimely warninghigh confidence
Under Investigation

At about 2:35 a.m. on February 7, 2026, a gunman robbed two people of their purses in the parking lot of Bayou Oaks at 5019 Calhoun Road, part of University of Houston on-campus housing. UH Police issued a security alert with a suspect description; the incident was the third armed robbery on or near campus in 2026, and some students complained the email notification arrived hours later.

Alerts
2
Response
Killed
Injured
Institution
University of Houston
Public R1 · TX
All UH cases →
~47,000 studentsUH Alert
Official alert policy
Read when and how UH says it will use UH ALERT: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

2 messages in sequence · 2 verified verbatim

Confirmed wording is transcribed character-for-character from a primary source. Use Verify this quote under each message to open that source in a new tab and compare the text yourself.

FOLLOW-UPEmail
Verified verbatim606 chars
Synopsis: On Saturday, February 7, 2026, at approximately 2:35am, UHPD responded to the report of an Aggravated Robbery that occurred in the parking lot of Bayou Oaks, at 5019 Calhoun Rd. The suspect approached complainants and displayed a firearm demanding their purses. He then fled west in the parking lot. Suspect #1: Black male, thin build, 5’6” height, gray jacket with hood, gray pants black tennis shoes, wearing a black surgical mask covering his face Weapon: Gray semi-automatic handgun. University of Houston Security Alerts are archived at www.uh.edu/police/safety-security/securityalerts
Classified timely-warning because the suspect had fled and the notice was a Clery continuing-threat warning, not an immediate shelter order.
Houston observes Central time; the 2:35 a.m. incident time is CST (UTC-6) in February.
Students told Click2Houston the email did not arrive until around 7:30 a.m., a notification-lag complaint preserved here as context rather than alert text.
Verbatim from UH ALERT official API rftContent for Security Alert CASE#26-0139 (Bayou Oaks aggravated robbery)
Message elements

How the first alert is built

To check this alert, Claude (an AI) read it in full 25 separate times, independently. Each read decided whether the message answers each of the six questions and gave a short reason. A final reviewer then weighed all 25 and wrote the plain-English verdict you see when you open a row. The score (for example 22/25) is how many reads agreed; the 25 individual reads are tucked underneath if you want to check them.

Security Alert - CASE#26-0139 - Aggravated Robbery- 5019 Calhoun Rd- See: www.uh.edu/police/safety-security/securityalerts

  • Sourcepresent18/25

    Final assessment

    A clear majority finds the link to uh.edu/police, paired with the 'Security Alert' label and case number, sufficient to identify University of Houston Police as the sender, though a notable minority felt no specific authority was explicitly named.

    Who is sending the alert and who is responding. People act faster on a message from a clearly identifiable, credible sender, such as a named department, the police, or a branded alert system, than on an anonymous notice. A branded signature counts.

    See all 25 individual reads
    1. absent: Only a case number and link, no named sender/authority in the text itself.
    2. present: Directs readers to "www.uh.edu/police/safety-security/securityalerts", identifying UH Police as issuer.
    3. present: Signed 'Security Alert', referencing University of Houston police case number and website.
    4. present: University of Houston Police security alert, referencing uh.edu/police.
    5. present: Branded 'Security Alert' with link to 'uh.edu/police'.
    6. present: Security Alert with case number, links to uh.edu/police.
    7. present: Attributed to 'uh.edu/police' with a case number.
    8. present: Labeled 'Security Alert' referencing 'uh.edu/police'.
    9. absent: "Security Alert" with case number but no named sending authority or branded alert system.
    10. present: References 'www.uh.edu/police', identifying UH police as the sender.
    11. present: Titled "Security Alert" pointing to UH police site.
    12. present: References uh.edu/police, University of Houston Police.
    13. present: Refers to uh.edu/police, University of Houston Police implied.
    14. present: References "uh.edu/police" as issuing authority.
    15. absent: Titled 'Security Alert' with a case number but no issuing agency named.
    16. absent: 'Security Alert' with case number but no specific issuing agency named
    17. present: Titled 'Security Alert' referencing 'www.uh.edu/police'.
    18. absent: Only labeled 'Security Alert' with a case number, no specific issuing authority named in text.
    19. present: Labeled 'Security Alert' and links to 'www.uh.edu/police', identifying UH police.
    20. present: Labeled 'Security Alert' referencing uh.edu/police.
    21. present: Labeled 'Security Alert' linking to uh.edu/police.
    22. absent: Generic 'Security Alert' with no named sender or authority beyond a case number and link.
    23. absent: 'Security Alert' with a case number but no named authority or agency.
    24. present: References uh.edu/police, University of Houston Police.
    25. present: Labeled "Security Alert" tied to "www.uh.edu/police".
  • Hazardpresent25/25

    Final assessment

    Unanimous agreement that 'Aggravated Robbery' names the specific crime/hazard.

    What the threat actually is. A complete warning names the specific danger, such as a shooter, a fire, a tornado, or a gas leak, rather than a vague emergency, because people decide what to do based on what they are facing.

    See all 25 individual reads
    1. present: Names 'Aggravated Robbery'.
    2. present: Names the crime as "Aggravated Robbery".
    3. present: Names 'Aggravated Robbery' specifically.
    4. present: Names 'Aggravated Robbery'.
    5. present: Names 'Aggravated Robbery'.
    6. present: Aggravated robbery named.
    7. present: Names 'Aggravated Robbery' as the incident.
    8. present: States 'Aggravated Robbery'.
    9. present: "Aggravated Robbery" named.
    10. present: Names 'Aggravated Robbery'.
    11. present: Names "Aggravated Robbery".
    12. present: Aggravated Robbery named.
    13. present: Names Aggravated Robbery.
    14. present: "Aggravated Robbery" named.
    15. present: Names 'Aggravated Robbery'.
    16. present: 'Aggravated Robbery'
    17. present: Names 'Aggravated Robbery'.
    18. present: States 'Aggravated Robbery'.
    19. present: States 'Aggravated Robbery'.
    20. present: Names 'Aggravated Robbery'.
    21. present: Names 'Aggravated Robbery'.
    22. present: 'Aggravated Robbery'.
    23. present: States 'Aggravated Robbery'.
    24. present: Aggravated Robbery.
    25. present: States "Aggravated Robbery".
  • Locationpresent25/25

    Final assessment

    All reads confirm the specific address, 5019 Calhoun Rd, is given.

    Where the threat is. Saying whether danger is in a specific building, a part of campus, or area-wide lets people judge their own proximity and choose a safe direction. Without a where, a warning is hard to act on precisely.

    See all 25 individual reads
    1. present: States '5019 Calhoun Rd'.
    2. present: Gives the address "5019 Calhoun Rd".
    3. present: Gives '5019 Calhoun Rd'.
    4. present: 5019 Calhoun Rd given.
    5. present: Gives '5019 Calhoun Rd'.
    6. present: 5019 Calhoun Rd given.
    7. present: Gives '5019 Calhoun Rd'.
    8. present: Gives '5019 Calhoun Rd'.
    9. present: "5019 Calhoun Rd".
    10. present: States '5019 Calhoun Rd'.
    11. present: Gives "5019 Calhoun Rd".
    12. present: 5019 Calhoun Rd.
    13. present: Gives 5019 Calhoun Rd.
    14. present: "5019 Calhoun Rd".
    15. present: Gives '5019 Calhoun Rd'.
    16. present: '5019 Calhoun Rd'
    17. present: Names '5019 Calhoun Rd'.
    18. present: Gives '5019 Calhoun Rd'.
    19. present: Names '5019 Calhoun Rd'.
    20. present: 5019 Calhoun Rd given.
    21. present: Gives '5019 Calhoun Rd'.
    22. present: '5019 Calhoun Rd'.
    23. present: Names '5019 Calhoun Rd'.
    24. present: 5019 Calhoun Rd.
    25. present: Names "5019 Calhoun Rd".
  • Guidanceabsent0/25

    Final assessment

    Unanimous agreement that no protective action is instructed, only a link to more information.

    The protective action to take. A clear, specific instruction, such as shelter in place, evacuate, avoid the area, or run-hide-fight, drives faster and more correct protective behavior than describing the threat alone.

    See all 25 individual reads
    1. absent: No protective action instruction given.
    2. absent: No protective action instruction is given.
    3. absent: No protective instruction given, only a link to more info.
    4. absent: No protective action instructed to recipients.
    5. absent: No protective action instructed.
    6. absent: No protective action instructed.
    7. absent: No protective action instructed to recipients.
    8. absent: No protective instruction given to recipients.
    9. absent: No protective action instructed, only a link to more info.
    10. absent: No instruction to the recipient is given.
    11. absent: No protective action instructed.
    12. absent: No protective action instructed to recipients.
    13. absent: No protective action instructed to recipients.
    14. absent: No protective action instructed, just points to a webpage.
    15. absent: No protective action instructed, just points to a website.
    16. absent: No protective action instructed, only points to a webpage
    17. absent: No protective action instruction given.
    18. absent: No protective instruction given.
    19. absent: No protective action instructed.
    20. absent: No protective action instruction to recipients.
    21. absent: No protective action instructed, just a case number and link.
    22. absent: No instruction given, only a link for more info.
    23. absent: No protective action instructed, just points to a webpage.
    24. absent: No protective action instructed.
    25. absent: No protective action instructed to recipients.
  • Timeabsent0/25

    Final assessment

    Unanimous agreement that no clock time or date is given in the message.

    When the message applies. A timestamp, the word now or immediately, or a phrase like until further notice tells the reader whether the danger is current and how quickly to act.

    See all 25 individual reads
    1. absent: No clock time or date given.
    2. absent: No date or clock time is given.
    3. absent: No time or date given in this short text.
    4. absent: No time or date given.
    5. absent: No clock time or date given.
    6. absent: No time given, only case number.
    7. absent: No clock time or date given.
    8. absent: No time or recency indicator given.
    9. absent: No time or date given.
    10. absent: No clock time or date is given, only a case number.
    11. absent: No clock time or recency marker given.
    12. absent: No clock time or date given in the text.
    13. absent: No clock time or date given.
    14. absent: No time given.
    15. absent: No time given.
    16. absent: No time given
    17. absent: No clock time or recency word given.
    18. absent: No time given.
    19. absent: No clock time or date given.
    20. absent: No time or date given beyond case number.
    21. absent: No time or date given.
    22. absent: No time/date given.
    23. absent: No clock time or date given.
    24. absent: No time or date given.
    25. absent: No clock time or recency marker given.
  • Impactabsent0/25

    Final assessment

    All reads agree no consequence or severity is stated.

    What the hazard could do to the people in its path. Beyond naming the threat, a complete warning conveys its potential consequences or severity, such as that a tornado can level buildings or that a leak could be explosive, so recipients grasp how much danger they are in. Research on warning message content finds that a concrete impact statement helps people personalize their risk and act sooner.

    See all 25 individual reads
    1. absent: No stated consequence conveyed.
    2. absent: No statement of potential harm or severity is included.
    3. absent: No stated consequence given.
    4. absent: No stated consequence or severity.
    5. absent: No stated consequence conveyed.
    6. absent: No stated consequence.
    7. absent: No statement of potential harm or severity.
    8. absent: No stated consequence or severity given.
    9. absent: No stated consequence conveyed.
    10. absent: No stated consequence or severity.
    11. absent: No stated consequence or severity given.
    12. absent: No stated consequence or severity.
    13. absent: No stated consequence given.
    14. absent: No stated consequence.
    15. absent: No stated consequence.
    16. absent: No stated consequence
    17. absent: No stated consequence or severity.
    18. absent: No stated consequence.
    19. absent: No stated consequence or severity.
    20. absent: No stated consequence.
    21. absent: No stated consequence.
    22. absent: No stated consequence.
    23. absent: No stated consequence described.
    24. absent: No stated consequence given.
    25. absent: No stated consequence or severity conveyed.

Systematic AI judgments with visible reasoning, not human-validated codings.

About this analysis
Context

Background

An aggravated robbery occurred around 2:35 a.m. CST on February 7, 2026 in the parking lot of Bayou Oaks at 5019 Calhoun Road, part of University of Houston on-campus housing. According to The Daily Cougar, the suspect pulled a gray semi-automatic handgun, demanded two people's purses, and fled west across the lot. UHPD circulated a suspect description—a thin Black male, about 5'6", in a gray hooded jacket and pants, black shoes, and a black surgical mask. The robbery was the third on or near campus in 2026, and some students told ABC13 and Click2Houston they were not alerted quickly enough, with the email reportedly arriving hours later. The case highlights both a clustering of armed robberies at one housing complex and recurring student frustration over Clery notification timing.
Analysis

Key Findings

The robbery was the third armed robbery on or near the UH campus in early 2026, clustering at the Bayou Oaks housing complex
UHPD issued a Clery timely warning with a detailed suspect description after the suspect fled
Students complained the email notice arrived hours after the 2:35 a.m. incident, reviving notification-timing concerns
No injuries occurred and no arrest had been announced as the investigation continued
Outcome
The suspect displayed a gray semi-automatic handgun, demanded two victims' purses, and fled west across the parking lot. No injuries were reported and the investigation was ongoing; no arrest had been announced.
Provenance

Sources

Every claim on this page is meant to be checkable. Open the links below (and the Verify this quote control under each confirmed alert) to read the original university, news, or archive page yourself. Hostnames are shown so you can see where you are going; archived copies survive when live pages move or disappear. See also our methodology.

  1. Student Paper
  2. News
  3. News
  4. Source
  5. Official
  6. Official
  7. Official
  8. Official
  9. Official
Cite this case

Campus Alert Archive. "University of Houston: Robbery, February 7, 2026." Incident of February 7, 2026. Added May 2026; last updated July 2026. https://campusalertarchive.com/case/university-of-houston-bayou-oaks-robbery-2026-02-07/

Download case JSON

Alert text quoted on this page remains the work of the issuing institution; the archive is a secondary source.

Tags
robberytimely-warningtexasarmed-robberyon-campus-housingnotification-delayUnder Investigation
Added May 2026Updated July 2026Via ingestion