Campus Alert Archive
NDSU

Light-blue Hyundai stolen from the RE Lot

AI-generated · every claim is source-linked
NDthefttimely warninghigh confidence
Compare →
Under Investigation

NDSU Police posted that a 2013 light-blue Hyundai Sonata was stolen from the RE Lot between 12:30 p.m. April 19 and 2:14 p.m. April 20.

Alerts
1
Response
—
Killed
—
Injured
—
Institution
North Dakota State University
Public R1 · ND
All NDSU cases →
NDSU Campus Emergency Notification System
Official alert policy
Read when and how NDSU says it will use NDSU CENS / NotiFind: summarized, quoted, and analyzed.
Documented Timeline

Alert Sequence

1 message in sequence · 1 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 ALERTEmail
Verified verbatim947 chars
April 19, 2026 - Motor Vehicle Theft Sometime between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026, a motor vehicle theft occurred in the RE lot at 1400 14th St N. A 2013 Light Blue Hyundai Sonata was stolen. Due to the vehicle make, model, and year it is likely that the method used is consistent with a widely reported trend involving similar vehicles. University Police are continuing the investigation of this theft. Vehicle Theft Prevention: Lock your vehicle and take your keys/FOB – do not leave vehicles running unattended. Remove valuables or keep them out of sight. Check with your vehicle manufacturer/dealer for anti-theft software updates or immobilizer/steering wheel lock options, especially if your model is known to be affected. Report all suspicious persons/activity immediately. If you have information that would assist the police investigation you are asked to call the NDSU Police at 231-8998.
Verify this quote
NDSU Police Safety Awareness Notices: April 19 2026 RE Lot MVTndsu.edufind archived copies
Dual independent HTML fetch 2026-08-24. sha256 b6ef570a5ca10414c75b5f4ff7cd1694850d38f3ef80be273ececcde392b2dca. Flattened from the April 19 accordion only. En dash after FOB preserved. SPN 429.
Distinct incident from 2026-04-24-north-dakota-state-university-re-lot-hyundai-theft-attempt: same lot, different color/completed vs attempted, different date window.
Distinct incident from 2026-04-18-north-dakota-state-university-r-lot-hyundai-theft-attempt: different lot (RE vs R), different vehicle (2013 light-blue Sonata vs 2016 blue Elantra), completed vs attempted.
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.

April 19, 2026 - Motor Vehicle Theft Sometime between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026, a motor vehicle theft occurred in the RE lot at 1400 14th St N. A 2013 Light Blue Hyundai Sonata was stolen. Due to the vehicle make, model, and year it is likely that the method used is consistent with a widely reported trend involving similar vehicles. University Police are continuing the investigation of this theft. Vehicle Theft Prevention: Lock your vehicle and take your keys/FOB – do not leave vehicles running unattended. Remove valuables or keep them out of sight. Check with your vehicle manufacturer/dealer for anti-theft software updates or immobilizer/steering wheel lock options, especially if your model is known to be affected. Report all suspicious persons/activity immediately. If you have information that would assist the police investigation you are asked to call the NDSU Police at 231-8998.

  • Sourcepresent25/25

    Final assessment

    University Police and NDSU Police are named as the investigating and publishing authority.

    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. present: The deciding words are "University Police", so this element is present.
    2. present: This read treats "University Police" as enough to mark the element present.
    3. present: Quoted evidence "University Police" is the specific language that carries the element.
    4. present: I mark present because the alert includes "University Police".
    5. present: Presence follows from the phrase "University Police" in the body.
    6. present: The message supplies "University Police", which satisfies the element on this pass.
    7. present: On this independent read, "University Police" is the hook that makes the element present.
    8. present: Element is present: the text itself contains "University Police".
    9. present: A first-time reader would see "University Police" and know the element is there.
    10. present: Coding present from the explicit wording "University Police".
    11. present: The body names it with "University Police", so the vote is present.
    12. present: This pass votes present on the strength of "University Police".
    13. present: Because the alert says "University Police", the element is not missing.
    14. present: The quoted span "University Police" is sufficient and does not need outside knowledge.
    15. present: Present: "University Police" is in the transmitted text.
    16. present: I am scoring present after locating "University Police" in the message.
    17. present: The element is carried by "University Police" rather than by implication alone.
    18. present: Direct language "University Police" is what this pass uses for a present vote.
    19. present: Nothing in the rest of the text undoes "University Police" as the present cue.
    20. present: This reviewer finds "University Police" and therefore records present.
    21. present: The alert is not silent here: it has "University Police".
    22. present: Present vote rests on the visible words "University Police".
    23. present: From the four corners of the message, "University Police" establishes the element.
    24. present: I quote "University Police" as the sole basis for present on this pass.
    25. present: Independent judgment: "University Police" is on the page, so present.
  • Hazardpresent25/25

    Final assessment

    motor vehicle theft is a specific named offense; a Hyundai Sonata was stolen.

    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: The deciding words are "motor vehicle theft", so this element is present.
    2. present: This read treats "motor vehicle theft" as enough to mark the element present.
    3. present: Quoted evidence "motor vehicle theft" is the specific language that carries the element.
    4. present: I mark present because the alert includes "motor vehicle theft".
    5. present: Presence follows from the phrase "motor vehicle theft" in the body.
    6. present: The message supplies "motor vehicle theft", which satisfies the element on this pass.
    7. present: On this independent read, "motor vehicle theft" is the hook that makes the element present.
    8. present: Element is present: the text itself contains "motor vehicle theft".
    9. present: A first-time reader would see "motor vehicle theft" and know the element is there.
    10. present: Coding present from the explicit wording "motor vehicle theft".
    11. present: The body names it with "motor vehicle theft", so the vote is present.
    12. present: This pass votes present on the strength of "motor vehicle theft".
    13. present: Because the alert says "motor vehicle theft", the element is not missing.
    14. present: The quoted span "motor vehicle theft" is sufficient and does not need outside knowledge.
    15. present: Present: "motor vehicle theft" is in the transmitted text.
    16. present: I am scoring present after locating "motor vehicle theft" in the message.
    17. present: The element is carried by "motor vehicle theft" rather than by implication alone.
    18. present: Direct language "motor vehicle theft" is what this pass uses for a present vote.
    19. present: Nothing in the rest of the text undoes "motor vehicle theft" as the present cue.
    20. present: This reviewer finds "motor vehicle theft" and therefore records present.
    21. present: The alert is not silent here: it has "motor vehicle theft".
    22. present: Present vote rests on the visible words "motor vehicle theft".
    23. present: From the four corners of the message, "motor vehicle theft" establishes the element.
    24. present: I quote "motor vehicle theft" as the sole basis for present on this pass.
    25. present: Independent judgment: "motor vehicle theft" is on the page, so present.
  • Locationpresent25/25

    Final assessment

    the RE lot at 1400 14th St N is a named place.

    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: The deciding words are "RE lot at 1400 14th St N", so this element is present.
    2. present: This read treats "RE lot at 1400 14th St N" as enough to mark the element present.
    3. present: Quoted evidence "RE lot at 1400 14th St N" is the specific language that carries the element.
    4. present: I mark present because the alert includes "RE lot at 1400 14th St N".
    5. present: Presence follows from the phrase "RE lot at 1400 14th St N" in the body.
    6. present: The message supplies "RE lot at 1400 14th St N", which satisfies the element on this pass.
    7. present: On this independent read, "RE lot at 1400 14th St N" is the hook that makes the element present.
    8. present: Element is present: the text itself contains "RE lot at 1400 14th St N".
    9. present: A first-time reader would see "RE lot at 1400 14th St N" and know the element is there.
    10. present: Coding present from the explicit wording "RE lot at 1400 14th St N".
    11. present: The body names it with "RE lot at 1400 14th St N", so the vote is present.
    12. present: This pass votes present on the strength of "RE lot at 1400 14th St N".
    13. present: Because the alert says "RE lot at 1400 14th St N", the element is not missing.
    14. present: The quoted span "RE lot at 1400 14th St N" is sufficient and does not need outside knowledge.
    15. present: Present: "RE lot at 1400 14th St N" is in the transmitted text.
    16. present: I am scoring present after locating "RE lot at 1400 14th St N" in the message.
    17. present: The element is carried by "RE lot at 1400 14th St N" rather than by implication alone.
    18. present: Direct language "RE lot at 1400 14th St N" is what this pass uses for a present vote.
    19. present: Nothing in the rest of the text undoes "RE lot at 1400 14th St N" as the present cue.
    20. present: This reviewer finds "RE lot at 1400 14th St N" and therefore records present.
    21. present: The alert is not silent here: it has "RE lot at 1400 14th St N".
    22. present: Present vote rests on the visible words "RE lot at 1400 14th St N".
    23. present: From the four corners of the message, "RE lot at 1400 14th St N" establishes the element.
    24. present: I quote "RE lot at 1400 14th St N" as the sole basis for present on this pass.
    25. present: Independent judgment: "RE lot at 1400 14th St N" is on the page, so present.
  • Guidancepresent25/25

    Final assessment

    Recipients are told to lock vehicles, report suspicious activity, and call 231-8998 with 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. present: The deciding words are "call the NDSU Police at 231-8998", so this element is present.
    2. present: This read treats "call the NDSU Police at 231-8998" as enough to mark the element present.
    3. present: Quoted evidence "call the NDSU Police at 231-8998" is the specific language that carries the element.
    4. present: I mark present because the alert includes "call the NDSU Police at 231-8998".
    5. present: Presence follows from the phrase "call the NDSU Police at 231-8998" in the body.
    6. present: The message supplies "call the NDSU Police at 231-8998", which satisfies the element on this pass.
    7. present: On this independent read, "call the NDSU Police at 231-8998" is the hook that makes the element present.
    8. present: Element is present: the text itself contains "call the NDSU Police at 231-8998".
    9. present: A first-time reader would see "call the NDSU Police at 231-8998" and know the element is there.
    10. present: Coding present from the explicit wording "call the NDSU Police at 231-8998".
    11. present: The body names it with "call the NDSU Police at 231-8998", so the vote is present.
    12. present: This pass votes present on the strength of "call the NDSU Police at 231-8998".
    13. present: Because the alert says "call the NDSU Police at 231-8998", the element is not missing.
    14. present: The quoted span "call the NDSU Police at 231-8998" is sufficient and does not need outside knowledge.
    15. present: Present: "call the NDSU Police at 231-8998" is in the transmitted text.
    16. present: I am scoring present after locating "call the NDSU Police at 231-8998" in the message.
    17. present: The element is carried by "call the NDSU Police at 231-8998" rather than by implication alone.
    18. present: Direct language "call the NDSU Police at 231-8998" is what this pass uses for a present vote.
    19. present: Nothing in the rest of the text undoes "call the NDSU Police at 231-8998" as the present cue.
    20. present: This reviewer finds "call the NDSU Police at 231-8998" and therefore records present.
    21. present: The alert is not silent here: it has "call the NDSU Police at 231-8998".
    22. present: Present vote rests on the visible words "call the NDSU Police at 231-8998".
    23. present: From the four corners of the message, "call the NDSU Police at 231-8998" establishes the element.
    24. present: I quote "call the NDSU Police at 231-8998" as the sole basis for present on this pass.
    25. present: Independent judgment: "call the NDSU Police at 231-8998" is on the page, so present.
  • Timepresent25/25

    Final assessment

    between 12:30 PM Sunday April 19 and 2:14 PM Monday April 20 is an explicit time window.

    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: The deciding words are "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026", so this element is present.
    2. present: This read treats "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" as enough to mark the element present.
    3. present: Quoted evidence "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" is the specific language that carries the element.
    4. present: I mark present because the alert includes "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026".
    5. present: Presence follows from the phrase "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" in the body.
    6. present: The message supplies "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026", which satisfies the element on this pass.
    7. present: On this independent read, "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" is the hook that makes the element present.
    8. present: Element is present: the text itself contains "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026".
    9. present: A first-time reader would see "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" and know the element is there.
    10. present: Coding present from the explicit wording "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026".
    11. present: The body names it with "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026", so the vote is present.
    12. present: This pass votes present on the strength of "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026".
    13. present: Because the alert says "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026", the element is not missing.
    14. present: The quoted span "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" is sufficient and does not need outside knowledge.
    15. present: Present: "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" is in the transmitted text.
    16. present: I am scoring present after locating "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" in the message.
    17. present: The element is carried by "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" rather than by implication alone.
    18. present: Direct language "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" is what this pass uses for a present vote.
    19. present: Nothing in the rest of the text undoes "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" as the present cue.
    20. present: This reviewer finds "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" and therefore records present.
    21. present: The alert is not silent here: it has "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026".
    22. present: Present vote rests on the visible words "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026".
    23. present: From the four corners of the message, "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" establishes the element.
    24. present: I quote "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" as the sole basis for present on this pass.
    25. present: Independent judgment: "between 12:30 PM, Sunday April 19, 2026, and 2:14 PM Monday, April 20, 2026" is on the page, so present.
  • Impactabsent0/25

    Final assessment

    The theft name is the hazard; there is no extra severity language such as dangerous.

    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: This pass finds no a stated harm or severity beyond naming the theft anywhere in the body, so the element is absent.
    2. absent: Absent: a full read never turns up a stated harm or severity beyond naming the theft.
    3. absent: The message never supplies a stated harm or severity beyond naming the theft, which this rubric requires.
    4. absent: I vote absent because a stated harm or severity beyond naming the theft is not in the transmitted text.
    5. absent: Nothing in the wording amounts to a stated harm or severity beyond naming the theft.
    6. absent: On this read the alert is silent on a stated harm or severity beyond naming the theft.
    7. absent: Absent follows from the lack of a stated harm or severity beyond naming the theft after reading the whole product.
    8. absent: A recipient would not learn a stated harm or severity beyond naming the theft from this text.
    9. absent: The element fails: a stated harm or severity beyond naming the theft does not appear.
    10. absent: I cannot mark present without a stated harm or severity beyond naming the theft, and it is not there.
    11. absent: This independent pass sees no a stated harm or severity beyond naming the theft to quote.
    12. absent: Coding absent; the body omits a stated harm or severity beyond naming the theft.
    13. absent: No clause in the alert does the work of a stated harm or severity beyond naming the theft.
    14. absent: The four corners of the message leave a stated harm or severity beyond naming the theft unspecified.
    15. absent: Absent vote: a stated harm or severity beyond naming the theft would have to be invented.
    16. absent: This reviewer looked for a stated harm or severity beyond naming the theft and did not find it.
    17. absent: The text stays at other facts and never reaches a stated harm or severity beyond naming the theft.
    18. absent: Without a stated harm or severity beyond naming the theft in the wording, the element is missing.
    19. absent: Present would need a stated harm or severity beyond naming the theft; that language is not used.
    20. absent: I record absent after confirming the product lacks a stated harm or severity beyond naming the theft.
    21. absent: The alert does not identify a stated harm or severity beyond naming the theft in any sentence.
    22. absent: Missing a stated harm or severity beyond naming the theft is the reason for the absent vote.
    23. absent: This pass will not infer a stated harm or severity beyond naming the theft from neighboring facts.
    24. absent: No quoted span equals a stated harm or severity beyond naming the theft, so absent.
    25. absent: Independent judgment: a stated harm or severity beyond naming the theft is not on the page.

Coded by SuperGrok Heavy 4.5

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

About this analysis
Context

Background

NDSU posted the notice on its Safety Awareness Notices page. Additional R-lot and UVS lot notices remain queued.
Analysis

Key Findings

A 2013 light-blue Hyundai Sonata was stolen from the RE Lot.
The notice ties the method to a widely reported trend involving similar vehicles.
Outcome
Completed theft. Distinct from the April 24 attempted theft of a red 2013 Sonata in the same lot.
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
    NDSU Safety Awareness Notices
    ndsu.edu
    archived copy
Cite this case

Campus Alert Archive. "North Dakota State University: Light-blue Hyundai stolen from the RE Lot." Incident of April 19, 2026. Added August 2026. https://campusalertarchive.com/case/north-dakota-state-university-re-lot-hyundai-theft-2026-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-r1north-dakotandsuthefttimely-warning2026Under Investigation
Added August 2026Updated August 2026Via ingestion