Campus Alert Archive
Oregon

Knife-armed robbery report at Franklin and Orchard

AI-generated · every claim is source-linked
ORrobberyemergency notificationhigh confidence
Compare →

UO Alert told the campus to avoid Franklin Blvd and Orchard St during a law-enforcement response, then posted an all-clear naming a knife-armed robbery at 2045 Franklin Blvd.

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 verbatim121 chars
12/11/2025 7:20PM AVOID Franklin Blvd. & Orchard St., Law Enforcement Activity. For updates, visit alerts.uoregon.edu.
Verify this quote
UO Alert Eugene AVOID Franklin Blvd. and Orchard St.safety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Drupal empty-paragraph runs collapsed to double newlines. Official double space after 12/11/2025 preserved. Second blind sha256 b6c2994fa98e0a0eda1310a08b0d8127e7a8e6303e3f8595fcdcff3f06355336.
Thread N/A (web posting, not X).
Distinct incident from 2025-12-08 East 12th/Patterson medical all-clear (different date and place) and from 2026-07-14 Franklin/Villard bicycle sexual-contact TW (different year, type, and block).
ALL CLEARWebsite+1h 10m
Verified verbatim627 chars
12/11/2025 at 8:30 ALL CLEAR - There is no longer law enforcement activity at Franklin Blvd. and Orchard St. Eugene PD received a report of a robbery that occurred at 2045 Franklin Blvd. The suspect was reported to be armed with a butcher-style knife. Suspect Description: • Unknown race, male, possibly in his 20s • Wearing a gray face mask, black backpack, black sweatshirt with a white T-shirt over it, blue jeans, and white shoes • Last seen leaving northeast from the back of the business Officers have checked the area and there is no ongoing threat to campus at this time. For updates, visit alerts.uoregon.edu.
Verify this quote
UO Alert Eugene ALL CLEAR Franklin and Orchardsafety.uoregon.edufind archived copies
Dual independent HTML fetch 2026-08-24. Official 8:30 with no AM/PM; sequenced after the 7:20 p.m. AVOID as evening. Bullet-tab characters preserved. Second blind sha256 52038095afd3c02f63c6c3726c6f4c42d3aaa31ee12b9e23a71d24a40c8ded52.
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.

12/11/2025 7:20PM AVOID Franklin Blvd. & Orchard St., Law Enforcement Activity. For updates, visit alerts.uoregon.edu.

  • Sourceabsent0/25

    Final assessment

    No branded sender in the Drupal AVOID body. 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: No branded UO Alert tag appears; the body opens with a date stamp then AVOID (UO Orchard AVOID, pass 1).
    2. absent: Source is absent: UO Alert Eugene is not in this Drupal product (UO Orchard AVOID, pass 2).
    3. absent: I code S 0 because the sender is not identified (UO Orchard AVOID, pass 3).
    4. absent: A date line is not a source signature (UO Orchard AVOID, pass 4).
    5. absent: I mark S absent (UO Orchard AVOID, pass 5).
    6. absent: Law Enforcement Activity is the hazard, not a sender (UO Orchard AVOID, pass 6).
    7. absent: Source fails (UO Orchard AVOID, pass 7).
    8. absent: I score S 0 (UO Orchard AVOID, pass 8).
    9. absent: No UOPD or UO Alert colon tag is in the text (UO Orchard AVOID, pass 9).
    10. absent: I find no branded signature (UO Orchard AVOID, pass 10).
    11. absent: S is 0 on this AVOID (UO Orchard AVOID, pass 11).
    12. absent: alerts.uoregon.edu is a URL not a sender brand (UO Orchard AVOID, pass 12).
    13. absent: I will not treat a URL as Source (UO Orchard AVOID, pass 13).
    14. absent: No police agency is named in the first-burst AVOID (UO Orchard AVOID, pass 14).
    15. absent: Source element is missing (UO Orchard AVOID, pass 15).
    16. absent: I read no sender identity (UO Orchard AVOID, pass 16).
    17. absent: Without UO Alert Eugene in this body, Source is absent (UO Orchard AVOID, pass 17).
    18. absent: I do not import twitter:title brand into the product (UO Orchard AVOID, pass 18).
    19. absent: S absent (UO Orchard AVOID, pass 19).
    20. absent: Named streets are location not source (UO Orchard AVOID, pass 20).
    21. absent: I code source absent (UO Orchard AVOID, pass 21).
    22. absent: Sender identity is unspecified (UO Orchard AVOID, pass 22).
    23. absent: S 0 (UO Orchard AVOID, pass 23).
    24. absent: The AVOID line does not name who is sending it (UO Orchard AVOID, pass 24).
    25. absent: No agency byline appears (UO Orchard AVOID, pass 25).
  • Hazardpresent25/25

    Final assessment

    Law Enforcement Activity names a specific situation. 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: Hazard is Law Enforcement Activity, a specific named situation (UO Orchard AVOID, pass 1).
    2. present: Law Enforcement Activity names the threat class (UO Orchard AVOID, pass 2).
    3. present: H is present (UO Orchard AVOID, pass 3).
    4. present: I count H 1 (UO Orchard AVOID, pass 4).
    5. present: Not a generic emergency (UO Orchard AVOID, pass 5).
    6. present: I mark H present (UO Orchard AVOID, pass 6).
    7. present: Named hazard: Law Enforcement Activity (UO Orchard AVOID, pass 7).
    8. present: H holds (UO Orchard AVOID, pass 8).
    9. present: I score H 1 (UO Orchard AVOID, pass 9).
    10. present: Police activity is specified (UO Orchard AVOID, pass 10).
    11. present: Hazard element is satisfied (UO Orchard AVOID, pass 11).
    12. present: I read Law Enforcement Activity as the hazard (UO Orchard AVOID, pass 12).
    13. present: H is 1 (UO Orchard AVOID, pass 13).
    14. present: The AVOID names law enforcement activity (UO Orchard AVOID, pass 14).
    15. present: Specific situation language is present (UO Orchard AVOID, pass 15).
    16. present: I treat Law Enforcement Activity as Hazard (UO Orchard AVOID, pass 16).
    17. present: H present (UO Orchard AVOID, pass 17).
    18. present: The product tells you what is happening (UO Orchard AVOID, pass 18).
    19. present: I code H 1 (UO Orchard AVOID, pass 19).
    20. present: Not a vague incident (UO Orchard AVOID, pass 20).
    21. present: Hazard is law enforcement activity (UO Orchard AVOID, pass 21).
    22. present: I find a named situation (UO Orchard AVOID, pass 22).
    23. present: H 1 (UO Orchard AVOID, pass 23).
    24. present: Law Enforcement Activity is specific (UO Orchard AVOID, pass 24).
    25. present: The threat class is named (UO Orchard AVOID, pass 25).
  • Locationpresent25/25

    Final assessment

    Franklin Blvd. and Orchard St. 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: Location is Franklin Blvd. and Orchard St., a named intersection (UO Orchard AVOID, pass 1).
    2. present: Franklin Blvd. and Orchard St. is a specific place (UO Orchard AVOID, pass 2).
    3. present: L is present (UO Orchard AVOID, pass 3).
    4. present: I count L 1 (UO Orchard AVOID, pass 4).
    5. present: Named streets satisfy location (UO Orchard AVOID, pass 5).
    6. present: I mark L present (UO Orchard AVOID, pass 6).
    7. present: Where: Franklin Blvd. and Orchard St (UO Orchard AVOID, pass 7).
    8. present: L holds (UO Orchard AVOID, pass 8).
    9. present: I score L 1 (UO Orchard AVOID, pass 9).
    10. present: An intersection is a place (UO Orchard AVOID, pass 10).
    11. present: Location element is satisfied (UO Orchard AVOID, pass 11).
    12. present: I read Franklin and Orchard as location (UO Orchard AVOID, pass 12).
    13. present: L is 1 (UO Orchard AVOID, pass 13).
    14. present: The AVOID names the intersection (UO Orchard AVOID, pass 14).
    15. present: Street-level location is present (UO Orchard AVOID, pass 15).
    16. present: I treat Franklin Blvd. and Orchard St. as location (UO Orchard AVOID, pass 16).
    17. present: Named place (UO Orchard AVOID, pass 17).
    18. present: L present (UO Orchard AVOID, pass 18).
    19. present: The site is specified (UO Orchard AVOID, pass 19).
    20. present: I code L 1 (UO Orchard AVOID, pass 20).
    21. present: Two named streets are a location (UO Orchard AVOID, pass 21).
    22. present: Where to avoid is named (UO Orchard AVOID, pass 22).
    23. present: Location is not omitted (UO Orchard AVOID, pass 23).
    24. present: I find a named intersection (UO Orchard AVOID, pass 24).
    25. present: L 1 (UO Orchard AVOID, 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: Guidance is AVOID, a protective instruction (UO Orchard AVOID, pass 1).
    2. present: AVOID tells recipients to stay away (UO Orchard AVOID, pass 2).
    3. present: G is present (UO Orchard AVOID, pass 3).
    4. present: I count G 1 (UO Orchard AVOID, pass 4).
    5. present: The text instructs people to avoid the intersection (UO Orchard AVOID, pass 5).
    6. present: I mark G present (UO Orchard AVOID, pass 6).
    7. present: Avoid-area guidance is in the rubric (UO Orchard AVOID, pass 7).
    8. present: G holds (UO Orchard AVOID, pass 8).
    9. present: I score G 1 (UO Orchard AVOID, pass 9).
    10. present: An imperative AVOID is guidance (UO Orchard AVOID, pass 10).
    11. present: Guidance element is satisfied (UO Orchard AVOID, pass 11).
    12. present: I read AVOID as the protective step (UO Orchard AVOID, pass 12).
    13. present: G is 1 (UO Orchard AVOID, pass 13).
    14. present: The product tells you what to do: avoid (UO Orchard AVOID, pass 14).
    15. present: I treat AVOID as guidance (UO Orchard AVOID, pass 15).
    16. present: Not merely status (UO Orchard AVOID, pass 16).
    17. present: G present (UO Orchard AVOID, pass 17).
    18. present: Recipients are instructed (UO Orchard AVOID, pass 18).
    19. present: I code G 1 (UO Orchard AVOID, pass 19).
    20. present: Stay away is the sense of AVOID (UO Orchard AVOID, pass 20).
    21. present: I find an instruction (UO Orchard AVOID, pass 21).
    22. present: Guidance is AVOID (UO Orchard AVOID, pass 22).
    23. present: I will count AVOID as G (UO Orchard AVOID, pass 23).
    24. present: G 1 (UO Orchard AVOID, pass 24).
    25. present: The AVOID line is protective (UO Orchard AVOID, pass 25).
  • Timepresent25/25

    Final assessment

    12/11/2025 7:20PM 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: 12/11/2025 7:20PM is an explicit date and clock time (UO Orchard AVOID, pass 1).
    2. present: T is present via 12/11/2025 and 7:20PM (UO Orchard AVOID, pass 2).
    3. present: I count T 1 (UO Orchard AVOID, pass 3).
    4. present: A clock time is listed in the rubric (UO Orchard AVOID, pass 4).
    5. present: I mark T present (UO Orchard AVOID, pass 5).
    6. present: The when is 7:20 p.m. December 11, 2025 (UO Orchard AVOID, pass 6).
    7. present: T holds (UO Orchard AVOID, pass 7).
    8. present: I score T 1 (UO Orchard AVOID, pass 8).
    9. present: Date and clock are in the first line (UO Orchard AVOID, pass 9).
    10. present: Time element is satisfied (UO Orchard AVOID, pass 10).
    11. present: I read 7:20PM as Time (UO Orchard AVOID, pass 11).
    12. present: T is 1 (UO Orchard AVOID, pass 12).
    13. present: A calendar date appears (UO Orchard AVOID, pass 13).
    14. present: I treat 12/11/2025 7:20PM as Time present (UO Orchard AVOID, pass 14).
    15. present: Without that stamp Time would fail (UO Orchard AVOID, pass 15).
    16. present: T present (UO Orchard AVOID, pass 16).
    17. present: Clock language is present (UO Orchard AVOID, pass 17).
    18. present: I code T 1 (UO Orchard AVOID, pass 18).
    19. present: The body names when (UO Orchard AVOID, pass 19).
    20. present: I find a date and clock (UO Orchard AVOID, pass 20).
    21. present: Time is 7:20PM (UO Orchard AVOID, pass 21).
    22. present: A date of the rubric kind is in the text (UO Orchard AVOID, pass 22).
    23. present: I will count 12/11/2025 as Time (UO Orchard AVOID, pass 23).
    24. present: T 1 (UO Orchard AVOID, pass 24).
    25. present: Date plus clock is Time (UO Orchard AVOID, pass 25).
  • Impactabsent0/25

    Final assessment

    No explicit 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: Impact is absent: no injury or severity is stated (UO Orchard AVOID, pass 1).
    2. absent: Law Enforcement Activity names the situation, not a harm clause (UO Orchard AVOID, pass 2).
    3. absent: I code I 0 (UO Orchard AVOID, pass 3).
    4. absent: AVOID is guidance not impact (UO Orchard AVOID, pass 4).
    5. absent: I mark I absent (UO Orchard AVOID, pass 5).
    6. absent: The rubric example list is not matched (UO Orchard AVOID, pass 6).
    7. absent: I find no harm sentence (UO Orchard AVOID, pass 7).
    8. absent: Impact fails (UO Orchard AVOID, pass 8).
    9. absent: I score I 0 (UO Orchard AVOID, pass 9).
    10. absent: Naming police activity is the hazard, not impact (UO Orchard AVOID, pass 10).
    11. absent: I 0 (UO Orchard AVOID, pass 11).
    12. absent: Consequence language is missing (UO Orchard AVOID, pass 12).
    13. absent: I decline to infer a robbery the first-burst omits (UO Orchard AVOID, pass 13).
    14. absent: Impact is not present (UO Orchard AVOID, pass 14).
    15. absent: I read no severity clause (UO Orchard AVOID, pass 15).
    16. absent: Without harm language, Impact is absent (UO Orchard AVOID, pass 16).
    17. absent: The AVOID does not state what the activity could do (UO Orchard AVOID, pass 17).
    18. absent: I code I absent (UO Orchard AVOID, pass 18).
    19. absent: No injury is named (UO Orchard AVOID, pass 19).
    20. absent: Impact element fails (UO Orchard AVOID, pass 20).
    21. absent: I will not invent a weapon from later sequence (UO Orchard AVOID, pass 21).
    22. absent: I 0 on this AVOID (UO Orchard AVOID, pass 22).
    23. absent: A named intersection is not impact (UO Orchard AVOID, pass 23).
    24. absent: I do not count police activity as impact (UO Orchard AVOID, pass 24).
    25. absent: Impact absent (UO Orchard AVOID, 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

Knife-armed robbery at 2045 Franklin Blvd; AVOID then ALL CLEAR the same evening.
Outcome
Officers checked the area; no ongoing threat to campus. Suspect description issued.
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 Franklin Blvd. and Orchard St.
    safety.uoregon.edu
    archived copy
  2. Official
    UO Alert Eugene ALL CLEAR Franklin and Orchard
    safety.uoregon.edu
    archived copy
Cite this case

Campus Alert Archive. "University of Oregon: Knife-armed robbery report at Franklin and Orchard." Incident of December 11, 2025. Added August 2026. https://campusalertarchive.com/case/university-of-oregon-franklin-orchard-armed-robbery-2025-12-11/

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-alertrobbery
Added August 2026Updated August 2026Via ingestion