Skip to main content
← Chains of Reasoning

Chain 4: He Could Not Have Sent the Discord Confession

:::caution Attributed claims only Tyler Robinson is charged, not convicted. Nothing here asserts that any named official fabricated a message. This is a chain of inference from documents — a defense filing, a booking sheet, a GRAMA hearing, and Discord's public statements — advanced by named investigators. It has not been adjudicated. :::

The conclusion this chain reaches

If the 6:25 PM Miranda warning on Bates 003996-R2 is dated September 11, 2025, then Tyler Robinson did not type "It was me at UVU yesterday." He was in an interview room, had asked for a lawyer, and no longer had a phone.

This is the chain the user of this site is most often asked to "just ignore." It does not require a theory of who did type the message. It requires two timestamps.

Link 1 — The official story needs him free, with a phone, at ~8 PM

The government's sequence, carried by Kash Patel's Senate testimony and every major outlet: Robinson was still at large on the evening of September 11. The FBI released "person of interest" photos at 7:55 PM. A Discord message from an account associated with him read "Hey guys, I have bad news for you all" and "It was me at UVU yesterday. im sorry for all of this" at roughly 7:57–8:00 PM — the circulating screenshot itself is also reported as 8:57 PM, which is still after every custody time at issue. Sheriff Nate Brooksby said he received his first call naming the suspect at 8:02 PM. Robinson then "turned himself in" around 9–10 PM. See Fed Claim 2 and Fed Claim 1. The message as published is photographs of a roommate's screen, not a native Discord export or a sworn statement — confession sourcing.

Strength: strong as a description of the official story. That is what the public was told.

A motion in State of Utah v. Tyler Robinson (case 251403576) quotes Bates-stamped video 003996-R2. An officer says "before we begin, I'm just gonna read you your rights" at a logged 06:25 PM. A minute later Robinson asks for counsel — naming Utah attorney Doug Terry — and declines further questions. The Miranda hub is Mirandize.

Attorney Baron Coleman put the stakes in one sentence the prosecution has never absorbed: the state's "entire narrative depends on him turning himself in after nine o'clock p.m."

Strength: strong as a document. Contested as to the date. The excerpt as circulated does not print a calendar date on the page. Everything below turns on that missing field.

Robinson says his parents are trying to reach the lawyer but "I think his office is closed for the night." September 11, 2025 was a Thursday. Coleman's argument: if this were 6:25 PM on Friday the 12th, a person would say the office was closed for the weekend. The phrasing also implies a recent conversation with his parents, which fits an arrival that evening rather than a full day already in a cell.

On X, Coleman did not hedge. April 8, 2026: "Tyler Robinson was in custody by 6:25p Utah Time on September 11, 2025. Anyone saying otherwise is FED SLOP" (@baroncoleman). May 11, 2026, 26,000 likes: he said he had confirmed Robinson was at the Washington County Sheriff's Office at 6:50 PM on September 11, and asked how it is "normal for people to post confessions to Discord AFTER they are in custody" (status/2053875761547747515).

Strength: moderate. Word-choice is an inference, not a stamp. It is the inference that currently does the most work.

The Utah County inmate sheet lists Arrest Date 09/11/2025 10:00 PM and Date In 09/12/2025 01:58 AM — a four-hour transport, which matches Washington County to Utah County. The arresting officer is SBI Agent Brian Davis, who would have started from the Provo–Salt Lake corridor. To take custody at 10 PM in Washington County, investigators argue he had to leave around 6:30 PM — which means somebody in northern Utah knew the location before Brooksby says he first heard the name at 8:02 PM.

Strength: strong if Davis's start point is Provo; checkable from a dispatch log that has not been produced.

Washington County told a state GRAMA hearing that a search for bodycam of the intake found none, despite Utah Code § 77-7a-104. The lobby CCTV of Robinson walking in has separately been described as no longer available. See bodycam GRAMA: no footage and missing surrender footage.

Strength: strong as a spoliation / absence fact; zero as proof of who typed a Discord message. It tells you the moment cannot now be watched.

On June 29, 2026, citizen journalist @DiligentDenizen posted, 12,900 likes: Robinson's parents say he told them he did not kill Charlie Kirk; they accompanied him to the sheriff in the afternoon of September 11; the phone was confiscated on arrival; neither Tyler nor his parents told the bishop or the sheriff that he did it. The follow-up question on the post is the whole chain: "How did Tyler send text 'confessions' if he was in police custody?"

That is the family-side version of Link 2. It is not a court finding. It is what citizen investigators have been repeating, month after month, since the filing surfaced.

Strength: moderate, attributed, and currently untested in open court.

Link 7 — Discord itself undercuts the "plotting" half of the same story

Discord's public position is that it found no evidence of planning on its platform. Patel nonetheless testified the FBI was investigating "anyone and everyone involved in that Discord chat" — more than twenty other users. The state has indicated it will not offer forensic extractions of the device in evidence. See state won't offer forensic extractions, the handle dispute, and confession sourcing.

A capital confession whose device record is not offered is a confession the defense cannot cross-examine. The same warrant package also names two different Discord usernames for the account — see the handle dispute — which is a separate attribution problem on top of the timestamp.

Strength: moderate. Companies minimise; prosecutors sometimes withhold extractions for reasons that have nothing to do with authenticity. Combined with Links 2–6, it is a different quality of problem.

Where the chain lands

Read the official order, then reverse the custody time:

Time (Sept 11, 2025)Official storyIf Bates 003996 is that evening
6:25 PMFree manMiranda; asks for a lawyer
7:55 PMFBI BOLO for a suspect at largeAlready in an interview room
~7:57 PMHe types the Discord confessionPhone is gone; he has invoked counsel
8:02 PMSheriff's "first call" naming himAlready in the building
10:00 PM"Turned himself in"Booking-sheet arithmetic, not a walk-in

Citizen investigators on X have been on this specific contradiction since the March 2026 filing, and they have not let go of it: April (Coleman, Diligent Denizen), May (Coleman "confirmed" 6:50 PM), June (family / phone confiscated), July ("already mirandized"), August (still the same two timestamps). The government's public sequence has not been restated to absorb it.

This chain does not identify who typed the message. It says the charged man, on this reading of the documents, did not.

The strongest objection to this whole chain

The date on Bates 003996-R2 is not printed on the excerpt. The state's position is that the warning occurred on September 12, after transport — which would put it eighteen hours after the Discord message and dissolve the contradiction. Commentator @TheAndyLoue (August 30, 2026) has separately argued the "06:25 PM" is an Axon Auto-Transcribe start-time plus elapsed-time misread, and that shifting a timezone puts rights at 12:25 AM September 12. Holding someone for hours before a formal booking is also lawful.

Those are real objections. What they have to explain, simultaneously, is "closed for the night" on a Thursday, an SBI officer 3.5 hours north taking custody at 10 PM, two camera systems with nothing, and a family account of an afternoon arrival and an immediate phone seizure. One innocent reading is cheap. Four at once is the price of keeping the confession.

What would settle it

  1. The date field on Bates 003996-R1/R2. One metadata tag ends this chain in either direction.
  2. Brian Davis's dispatch and travel record for September 11.
  3. The written reports Utah Code § 77-7a-104(10) requires from every deputy whose camera was off.
  4. The device extraction, offered in court, with timezone and send-server logs.