Campus Alert Archive
Oregon

Shooting search at 18th and Agate then cleared

AI-generated · every claim is source-linked
ORshootingemergency notificationhigh confidence
Compare →
Under Investigation

UO Alert told the campus to avoid 18th and Agate for a shooting, then posted an all-clear with a metal-baton assault at Student Manor Apartments and reports of gunshots.

Alerts
2
Response
—
Killed
—
Injured
—
Institution
University of Oregon
Public R1 · OR
All Oregon cases →
UO Alert
Official alert policy
Read when and how Oregon says it will use UO 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.

INITIAL ALERTWebsite
Verified verbatim134 chars
04/19/2025 4:11 AVOID 18th & Agate, Shooting occurred. Police are searching for the suspect. More information on alerts.uoregon.edu.
Verify this quote
UO Alert Eugene: AVOID 18th and Agate shootingsafety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Clock 4:11 with all-clear at 5:41 a.m. read as 4:11 a.m. Official Drupal URL spelling occured; body uses occurred. Second blind sha256 4507a15978e4d2f9208b3e23d5c26b64520fe36d0f994c2cebd2dfbed794c2a1.
Thread N/A (web posting, not X).
Distinct incident from 2025-10-25-university-of-oregon-18th-agate-police-activity: same intersection, different date and year-month.
ALL CLEARWebsite+1h 30m
Verified verbatim649 chars
04/19/2025 5:41 a.m. At 3:35 a.m., Saturday morning, a person was transported to the hospital for injuries after being hit in the head by a metal baton-like object at the Student Manor Apartments at 18th and Agate. The victim was located at 19th and Emerald. There were also reports of gun shots being heard. The victim and suspect know each other. The suspect is described as a white male, bald, wearing all black, last seen running south on Agate St. If you have any information regarding the incident or suspect's identity, contact EPD at the non-emergency number 541-682-5111. Any additional information will be shared at alerts.uoregon.edu.
Verify this quote
UO Alert Eugene: All Clear 18th and Agatesafety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Official curly apostrophe in suspect's preserved. Second blind sha256 ed91dd1a5c2a23864feb06a0c67d885e74dcadd6d974a03b4e631f17be3bd5b1.
Message elements

How the first alert is built

To check this alert, SuperGrok Heavy 4.5 (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.

04/19/2025 4:11 AVOID 18th & Agate, Shooting occurred. Police are searching for the suspect. More information on alerts.uoregon.edu.

  • Sourceabsent0/25

    Final assessment

    No branded sender in the Drupal AVOID. Majority 0/25.

    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: I read no branded UO Alert tag in this Drupal AVOID in this first burst (no branded UO Alert , pass 1).
    2. absent: No branded UO Alert tag in this Drupal AVOID is present on my read (no branded UO Alert , pass 2).
    3. absent: I score this element from no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 3).
    4. absent: The deciding words are no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 4).
    5. absent: Verdict follows no branded UO Alert tag in this Drupal AVOID in the body (no branded UO Alert , pass 5).
    6. absent: I mark this from no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 6).
    7. absent: No branded UO Alert tag in this Drupal AVOID satisfies the rubric here (no branded UO Alert , pass 7).
    8. absent: My pass treats no branded UO Alert tag in this Drupal AVOID as the cue (no branded UO Alert , pass 8).
    9. absent: I find no branded UO Alert tag in this Drupal AVOID and code accordingly (no branded UO Alert , pass 9).
    10. absent: Element turns on no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 10).
    11. absent: I count this because of no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 11).
    12. absent: The text gives no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 12).
    13. absent: I rely on no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 13).
    14. absent: Present or absent per no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 14).
    15. absent: I do not need more than no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 15).
    16. absent: Coding follows no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 16).
    17. absent: I note no branded UO Alert tag in this Drupal AVOID as the tell (no branded UO Alert , pass 17).
    18. absent: This pass keys off no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 18).
    19. absent: I take no branded UO Alert tag in this Drupal AVOID as sufficient (no branded UO Alert , pass 19).
    20. absent: The body states no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 20).
    21. absent: I judge from no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 21).
    22. absent: No branded UO Alert tag in this Drupal AVOID is the evidence I use (no branded UO Alert , pass 22).
    23. absent: I apply the rubric to no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 23).
    24. absent: My reason is no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 24).
    25. absent: I close on no branded UO Alert tag in this Drupal AVOID (no branded UO Alert , pass 25).
  • Hazardpresent25/25

    Final assessment

    Shooting names a specific hazard. Majority 25/25.

    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: I read a shooting as the named hazard in this first burst (a shooting as the na, pass 1).
    2. present: A shooting as the named hazard is present on my read (a shooting as the na, pass 2).
    3. present: I score this element from a shooting as the named hazard (a shooting as the na, pass 3).
    4. present: The deciding words are a shooting as the named hazard (a shooting as the na, pass 4).
    5. present: Verdict follows a shooting as the named hazard in the body (a shooting as the na, pass 5).
    6. present: I mark this from a shooting as the named hazard (a shooting as the na, pass 6).
    7. present: A shooting as the named hazard satisfies the rubric here (a shooting as the na, pass 7).
    8. present: My pass treats a shooting as the named hazard as the cue (a shooting as the na, pass 8).
    9. present: I find a shooting as the named hazard and code accordingly (a shooting as the na, pass 9).
    10. present: Element turns on a shooting as the named hazard (a shooting as the na, pass 10).
    11. present: I count this because of a shooting as the named hazard (a shooting as the na, pass 11).
    12. present: The text gives a shooting as the named hazard (a shooting as the na, pass 12).
    13. present: I rely on a shooting as the named hazard (a shooting as the na, pass 13).
    14. present: Present or absent per a shooting as the named hazard (a shooting as the na, pass 14).
    15. present: I do not need more than a shooting as the named hazard (a shooting as the na, pass 15).
    16. present: Coding follows a shooting as the named hazard (a shooting as the na, pass 16).
    17. present: I note a shooting as the named hazard as the tell (a shooting as the na, pass 17).
    18. present: This pass keys off a shooting as the named hazard (a shooting as the na, pass 18).
    19. present: I take a shooting as the named hazard as sufficient (a shooting as the na, pass 19).
    20. present: The body states a shooting as the named hazard (a shooting as the na, pass 20).
    21. present: I judge from a shooting as the named hazard (a shooting as the na, pass 21).
    22. present: A shooting as the named hazard is the evidence I use (a shooting as the na, pass 22).
    23. present: I apply the rubric to a shooting as the named hazard (a shooting as the na, pass 23).
    24. present: My reason is a shooting as the named hazard (a shooting as the na, pass 24).
    25. present: I close on a shooting as the named hazard (a shooting as the na, pass 25).
  • Locationpresent25/25

    Final assessment

    18th and Agate is a named intersection. Majority 25/25.

    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: I read 18th and Agate as the named intersection in this first burst (18th and Agate as th, pass 1).
    2. present: 18th and Agate as the named intersection is present on my read (18th and Agate as th, pass 2).
    3. present: I score this element from 18th and Agate as the named intersection (18th and Agate as th, pass 3).
    4. present: The deciding words are 18th and Agate as the named intersection (18th and Agate as th, pass 4).
    5. present: Verdict follows 18th and Agate as the named intersection in the body (18th and Agate as th, pass 5).
    6. present: I mark this from 18th and Agate as the named intersection (18th and Agate as th, pass 6).
    7. present: 18th and Agate as the named intersection satisfies the rubric here (18th and Agate as th, pass 7).
    8. present: My pass treats 18th and Agate as the named intersection as the cue (18th and Agate as th, pass 8).
    9. present: I find 18th and Agate as the named intersection and code accordingly (18th and Agate as th, pass 9).
    10. present: Element turns on 18th and Agate as the named intersection (18th and Agate as th, pass 10).
    11. present: I count this because of 18th and Agate as the named intersection (18th and Agate as th, pass 11).
    12. present: The text gives 18th and Agate as the named intersection (18th and Agate as th, pass 12).
    13. present: I rely on 18th and Agate as the named intersection (18th and Agate as th, pass 13).
    14. present: Present or absent per 18th and Agate as the named intersection (18th and Agate as th, pass 14).
    15. present: I do not need more than 18th and Agate as the named intersection (18th and Agate as th, pass 15).
    16. present: Coding follows 18th and Agate as the named intersection (18th and Agate as th, pass 16).
    17. present: I note 18th and Agate as the named intersection as the tell (18th and Agate as th, pass 17).
    18. present: This pass keys off 18th and Agate as the named intersection (18th and Agate as th, pass 18).
    19. present: I take 18th and Agate as the named intersection as sufficient (18th and Agate as th, pass 19).
    20. present: The body states 18th and Agate as the named intersection (18th and Agate as th, pass 20).
    21. present: I judge from 18th and Agate as the named intersection (18th and Agate as th, pass 21).
    22. present: 18th and Agate as the named intersection is the evidence I use (18th and Agate as th, pass 22).
    23. present: I apply the rubric to 18th and Agate as the named intersection (18th and Agate as th, pass 23).
    24. present: My reason is 18th and Agate as the named intersection (18th and Agate as th, pass 24).
    25. present: I close on 18th and Agate as the named intersection (18th and Agate as th, pass 25).
  • Guidancepresent25/25

    Final assessment

    AVOID is a protective instruction. Majority 25/25.

    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. present: I read AVOID as the protective instruction in this first burst (AVOID as the protect, pass 1).
    2. present: AVOID as the protective instruction is present on my read (AVOID as the protect, pass 2).
    3. present: I score this element from AVOID as the protective instruction (AVOID as the protect, pass 3).
    4. present: The deciding words are AVOID as the protective instruction (AVOID as the protect, pass 4).
    5. present: Verdict follows AVOID as the protective instruction in the body (AVOID as the protect, pass 5).
    6. present: I mark this from AVOID as the protective instruction (AVOID as the protect, pass 6).
    7. present: AVOID as the protective instruction satisfies the rubric here (AVOID as the protect, pass 7).
    8. present: My pass treats AVOID as the protective instruction as the cue (AVOID as the protect, pass 8).
    9. present: I find AVOID as the protective instruction and code accordingly (AVOID as the protect, pass 9).
    10. present: Element turns on AVOID as the protective instruction (AVOID as the protect, pass 10).
    11. present: I count this because of AVOID as the protective instruction (AVOID as the protect, pass 11).
    12. present: The text gives AVOID as the protective instruction (AVOID as the protect, pass 12).
    13. present: I rely on AVOID as the protective instruction (AVOID as the protect, pass 13).
    14. present: Present or absent per AVOID as the protective instruction (AVOID as the protect, pass 14).
    15. present: I do not need more than AVOID as the protective instruction (AVOID as the protect, pass 15).
    16. present: Coding follows AVOID as the protective instruction (AVOID as the protect, pass 16).
    17. present: I note AVOID as the protective instruction as the tell (AVOID as the protect, pass 17).
    18. present: This pass keys off AVOID as the protective instruction (AVOID as the protect, pass 18).
    19. present: I take AVOID as the protective instruction as sufficient (AVOID as the protect, pass 19).
    20. present: The body states AVOID as the protective instruction (AVOID as the protect, pass 20).
    21. present: I judge from AVOID as the protective instruction (AVOID as the protect, pass 21).
    22. present: AVOID as the protective instruction is the evidence I use (AVOID as the protect, pass 22).
    23. present: I apply the rubric to AVOID as the protective instruction (AVOID as the protect, pass 23).
    24. present: My reason is AVOID as the protective instruction (AVOID as the protect, pass 24).
    25. present: I close on AVOID as the protective instruction (AVOID as the protect, pass 25).
  • Timepresent25/25

    Final assessment

    04/19/2025 4:11 is a date and clock. Majority 25/25.

    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. present: I read 04/19/2025 4:11 as date and clock in this first burst (04/19/2025 4:11 as d, pass 1).
    2. present: 04/19/2025 4:11 as date and clock is present on my read (04/19/2025 4:11 as d, pass 2).
    3. present: I score this element from 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 3).
    4. present: The deciding words are 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 4).
    5. present: Verdict follows 04/19/2025 4:11 as date and clock in the body (04/19/2025 4:11 as d, pass 5).
    6. present: I mark this from 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 6).
    7. present: 04/19/2025 4:11 as date and clock satisfies the rubric here (04/19/2025 4:11 as d, pass 7).
    8. present: My pass treats 04/19/2025 4:11 as date and clock as the cue (04/19/2025 4:11 as d, pass 8).
    9. present: I find 04/19/2025 4:11 as date and clock and code accordingly (04/19/2025 4:11 as d, pass 9).
    10. present: Element turns on 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 10).
    11. present: I count this because of 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 11).
    12. present: The text gives 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 12).
    13. present: I rely on 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 13).
    14. present: Present or absent per 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 14).
    15. present: I do not need more than 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 15).
    16. present: Coding follows 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 16).
    17. present: I note 04/19/2025 4:11 as date and clock as the tell (04/19/2025 4:11 as d, pass 17).
    18. present: This pass keys off 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 18).
    19. present: I take 04/19/2025 4:11 as date and clock as sufficient (04/19/2025 4:11 as d, pass 19).
    20. present: The body states 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 20).
    21. present: I judge from 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 21).
    22. present: 04/19/2025 4:11 as date and clock is the evidence I use (04/19/2025 4:11 as d, pass 22).
    23. present: I apply the rubric to 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 23).
    24. present: My reason is 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 24).
    25. present: I close on 04/19/2025 4:11 as date and clock (04/19/2025 4:11 as d, pass 25).
  • Impactabsent0/25

    Final assessment

    No consequence in the first-burst AVOID. Majority 0/25.

    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: I read no injury clause in the first-burst AVOID in this first burst (no injury clause in , pass 1).
    2. absent: No injury clause in the first-burst AVOID is present on my read (no injury clause in , pass 2).
    3. absent: I score this element from no injury clause in the first-burst AVOID (no injury clause in , pass 3).
    4. absent: The deciding words are no injury clause in the first-burst AVOID (no injury clause in , pass 4).
    5. absent: Verdict follows no injury clause in the first-burst AVOID in the body (no injury clause in , pass 5).
    6. absent: I mark this from no injury clause in the first-burst AVOID (no injury clause in , pass 6).
    7. absent: No injury clause in the first-burst AVOID satisfies the rubric here (no injury clause in , pass 7).
    8. absent: My pass treats no injury clause in the first-burst AVOID as the cue (no injury clause in , pass 8).
    9. absent: I find no injury clause in the first-burst AVOID and code accordingly (no injury clause in , pass 9).
    10. absent: Element turns on no injury clause in the first-burst AVOID (no injury clause in , pass 10).
    11. absent: I count this because of no injury clause in the first-burst AVOID (no injury clause in , pass 11).
    12. absent: The text gives no injury clause in the first-burst AVOID (no injury clause in , pass 12).
    13. absent: I rely on no injury clause in the first-burst AVOID (no injury clause in , pass 13).
    14. absent: Present or absent per no injury clause in the first-burst AVOID (no injury clause in , pass 14).
    15. absent: I do not need more than no injury clause in the first-burst AVOID (no injury clause in , pass 15).
    16. absent: Coding follows no injury clause in the first-burst AVOID (no injury clause in , pass 16).
    17. absent: I note no injury clause in the first-burst AVOID as the tell (no injury clause in , pass 17).
    18. absent: This pass keys off no injury clause in the first-burst AVOID (no injury clause in , pass 18).
    19. absent: I take no injury clause in the first-burst AVOID as sufficient (no injury clause in , pass 19).
    20. absent: The body states no injury clause in the first-burst AVOID (no injury clause in , pass 20).
    21. absent: I judge from no injury clause in the first-burst AVOID (no injury clause in , pass 21).
    22. absent: No injury clause in the first-burst AVOID is the evidence I use (no injury clause in , pass 22).
    23. absent: I apply the rubric to no injury clause in the first-burst AVOID (no injury clause in , pass 23).
    24. absent: My reason is no injury clause in the first-burst AVOID (no injury clause in , pass 24).
    25. absent: I close on no injury clause in the first-burst AVOID (no injury clause in , pass 25).

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

University of Oregon posts UO Alert products on safety.uoregon.edu/alerts.
Analysis

Key Findings

AVOID 18th and Agate 4:11 a.m. for a shooting; 5:41 a.m. all-clear names a baton assault at Student Manor and reports of gunshots.
Outcome
Victim transported; suspect described running south on Agate. Official URL spelling occured; body uses occurred.
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. Official
    UO Alert Eugene: AVOID 18th and Agate shooting
    safety.uoregon.edu
    archived copy
  2. Official
    UO Alert Eugene: All Clear 18th and Agate
    safety.uoregon.edu
    archived copy
Cite this case

Campus Alert Archive. "University of Oregon: Shooting search at 18th and Agate then cleared." Incident of April 19, 2025. Added August 2026. https://campusalertarchive.com/case/university-of-oregon-18th-agate-shooting-2025-04-19/

Download case JSON

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

Tags
public-r1oregonuo-alertshootingUnder Investigation
Added August 2026Updated August 2026Via ingestion