Skip to content
Campus Alert Archive
NDSU

Gray Pontiac Grand Am stolen from the HR Lot

AI-generated · every claim is source-linked
NDthefttimely warninghigh confidence

NDSU Police posted that a 2008 gray Pontiac Grand Am was stolen from the HR Lot between October 19 and 22 and that the vehicle has been recovered.

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 verbatim722 chars
October 25, 2024 - Motor Vehicle Theft On 10/24/2024 NDSU Police were informed of a motor vehicle theft involving a 2008 Gray Pontiac Grand Am. Through the investigation it was determined that this vehicle was stolen from the HR-Lot sometime between 5:30 p.m. Saturday, October 19th and 11:30 p.m. Tuesday, October 22nd. The vehicle has been recovered and University police are continuing the investigation into this theft. Please remember to lock your vehicles and secure your keys and other valuables. If you have information that would assist the police investigation you are asked to call the NDSU Police at 231-8998. This message is authorized and transmitted by the University Police Communications Call Center.
Dual independent HTML fetch 2026-08-24. sha256 2330ccabdc485214442ec3f9f3f0a630ab91bd3f8a06306f7865a8fbb9be524b. Flattened from the October 25 2024 accordion only. SPN 429.
Distinct incident from 2024-10-28-north-dakota-state-university-r-lot-chevy-blazer-theft: different lot (HR vs R), different vehicle, different date window (Oct 19-22 vs Oct 27-28).
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.

October 25, 2024 - Motor Vehicle Theft On 10/24/2024 NDSU Police were informed of a motor vehicle theft involving a 2008 Gray Pontiac Grand Am. Through the investigation it was determined that this vehicle was stolen from the HR-Lot sometime between 5:30 p.m. Saturday, October 19th and 11:30 p.m. Tuesday, October 22nd. The vehicle has been recovered and University police are continuing the investigation into this theft. Please remember to lock your vehicles and secure your keys and other valuables. If you have information that would assist the police investigation you are asked to call the NDSU Police at 231-8998. This message is authorized and transmitted by the University Police Communications Call Center.

  • Sourcepresent25/25

    Final assessment

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

    Final assessment

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

    Final assessment

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

    Final assessment

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

    Final assessment

    The theft name is the hazard; recovered does not add 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. Remaining September 2024 shots-fired notices queued.
Analysis

Key Findings

A 2008 gray Pontiac Grand Am was stolen from the HR Lot and has been recovered.
The notice is authorized by the University Police Communications Call Center.
Outcome
Completed theft; vehicle recovered. Distinct from the October 28 R-lot Chevy Blazer theft on the same page.
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
Cite this case

Campus Alert Archive. "North Dakota State University: Gray Pontiac Grand Am stolen from the HR Lot." Incident of October 25, 2024. Added August 2026. https://campusalertarchive.com/case/north-dakota-state-university-hr-lot-pontiac-grand-am-theft-2024-10-25/

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