The NAUT X intel snapshot is the X account record NAUT keeps on a company row: a stored follower count, the timestamp that count was read, and the trail of handles the account has used. NAUT's data shows 8,811 of 10,592 live company rows carry a stored follower count and 178 carry a handle trail, read on 11 November 2026, with the follower counts themselves read between 30 May 2026 and 6 November 2026.
3 live NAUT articles run off these same fields: the engagement check, the fake-follower check and the handle-change check. This piece opens the fields up, says what each one can and cannot tell a deal maker, and works 1 example row end to end.
Data note. Every figure here comes from NAUT's own company records, read on 11 November 2026, scoped to live rows that are not archived and not merged into another row. 5 outside claims were put to public sources for this article: 4 came back confirmed and are used below, and 1 (the chain behind the worked example's stored token mint) came back confirmed on a page whose wording could not be located, so that mint is printed only as the value NAUT stores. GMGN's own token pages returned HTTP 403 to NAUT's fetch on 9 November 2026, and so did solscan.io token pages, so the handle trail is read from NAUT's stored copy of it. Written by the NAUT data team.
What is the NAUT X intel snapshot, and which 3 fields hold it?
The snapshot is 3 stored fields on the company row, plus 1 paired field of flags. Each is filled by a background job, so each carries its own age. The table below is ordered by how many live rows carry the field.
| Field | What it holds | Live rows |
|---|---|---|
followers |
The X follower count read at the time of the check | 8,811 of 10,592 |
followersCheckedAt |
The timestamp that count was read | 6,314 of 10,592 |
gmgnHandleHistory |
The trail of X handles tied to the account | 178 of 10,592 |
gmgnTwitterFlags |
Token mint, chain, CTO flag and account activity counts | 199 of 10,592 |
What a deal maker does with each: followers sizes the audience before a pitch, followersCheckedAt dates the number before you quote it, gmgnHandleHistory spots a renamed or reused account, and gmgnTwitterFlags reads how the account behaves on-chain.
2 limits sit in that table and both matter before you quote a number. The follower count is a point reading, so a crypto project follower history on NAUT is the set of readings taken so far, never a continuous series. And 6,314 of the 8,811 stored counts carry a check timestamp, so for the rest the reading is on file and its date is not, which is why every follower figure in a NAUT article is printed with the date it was read.
The handle trail is the narrow field of the 4. It is filled from GMGN rename records, which cover accounts tied to a Solana token mint, so it reaches token projects far more often than equity-stage startups. GMGN is a Solana token tracking platform that records on-chain token data alongside the X activity tied to those tokens (Medium write-up, GMGN's own tracking post).
How many rows carry a NAUT X intel snapshot?
Of the 178 live rows with a handle trail, 89 carry 2 or more handles, which is the set where an X handle change check has something to read. 199 rows carry the paired flags field, and 16 of those carry the CTO flag, GMGN's marker that an abandoned token was picked up by its holders. The crypto.news explainer defines that event as "When the holders of an abandoned token band together and run it themselves after the original developer walks away."
The 10 longest trails on file run from 8 handles down to 4. The list is ranked by the number of handles on the trail, with the stored follower count and its check date beside it.
| Project | Handles | Followers | Read on |
|---|---|---|---|
 MemeCore |
8 | 42,786 | 23 September 2026 |
 Sidekick |
6 | 520,872 | 30 May 2026 |
 TaleX |
6 | 197,809 | 30 May 2026 |
 OVERTAKE |
5 | 271,387 | 30 May 2026 |
 aPriori |
5 | 197,205 | 30 May 2026 |
 Avantis |
5 | 104,174 | 30 May 2026 |
 Maiga |
5 | 96,905 | 30 May 2026 |
 Arkham |
4 | 1,527,557 | 30 May 2026 |
 SoSoValue |
4 | 1,009,813 | 30 May 2026 |
 GoPlus Security |
4 | 449,396 | 30 May 2026 |
None of those 10 rows carries the CTO flag, so a long trail on its own says the account was renamed, and it says nothing about who runs the project today. 9 of the 10 counts were read on 30 May 2026 and 1 on 23 September 2026, which is the spread you should expect across the whole set: the oldest check on any live row is 30 May 2026 and the newest is 6 November 2026.
Anyone listed can ask NAUT to remove their page at https://naut.so/legal/data-deletion.
Handles on the trail, the 10 longest on file
Each bar is the count of handles NAUT holds for that account, so a bar of 8 means 7 renames are on record for the row with the longest trail.
How the snapshot reads on 1 project
Caesar carries all 4 fields, which makes it the cleanest way to read a snapshot line by line.
- Stored followers: 10,325, read on 30 May 2026.
- Handles on the trail: 2. The record shows @telenomic dated 14 January 2025 and @caesar_data dated 10 May 2025.
- Flags, read on 31 May 2026: CTO flag on, 91 token-creating posts, 1 deleted token post, 0 duplicate images.
- Stored mint:
G4uJcvo5UAJ3fU1gj96e5DjBJU2RDDPx9Txzbjw6Y3LA, with the chain field set tosol. - NAUT's stored description: a deep research assistant powered by AI.
The outside check lines up with the newer half of that trail. The account at x.com/caesar_data is live and is the X account of an organisation called Caesar, and its profile links the domain caesar.xyz, which belongs to Caesar Data, Inc. So the snapshot's current handle is right as of the check, and the renamed older handle is the part a researcher has to read with care: a 2 handle trail plus a CTO flag describes the token account's history, and the company behind the current handle has to be confirmed on its own site, as it was here.
That is the discipline the whole field asks for. Treat crypto Twitter intel as a pointer to a question, then answer the question on the company's own property.
What this tells a BD team
- A stored follower count without a recent date works for sizing an audience and little else. 6,314 of the 8,811 counts carry a check date, so quote the date beside the number every time.
- A handle trail of 2 or more is a reason to re-read the account before you write the first line of an email. 89 live rows are in that bucket.
- The CTO flag is the loudest signal in the set and the rarest: 16 live rows carry it. A flagged row means the original developer walked away, so the person on your list may no longer be the person running it.
- An empty trail carries no verdict either way. 178 of 10,592 rows carry a trail at all, so most rows simply have no GMGN record to read.
- Read the date first6,314 of 8,811 stored follower counts carry a check timestamp, and the oldest check on file is 30 May 2026.
- Check the trail89 live rows hold 2 or more handles, from MemeCore at 8 down to 4.
- Screen the flag16 live rows carry the CTO flag, so re-confirm who runs the project before you pitch it.
- Confirm on the company's own siteCaesar resolved to caesar.xyz and Caesar Data, Inc. from its X profile link.
What this tells a founder raising
- An investor sourcing your round can see your stored follower count and the date it was read. On Arkham that is 1,527,557 read on 30 May 2026, and a figure that old will be re-checked before a term sheet.
- If your project has renamed its X account, the rename is on record. 7 renames sit behind the longest trail on file.
- A CTO flag on your row is worth answering before a call rather than during it, because the flag says an abandoned token was taken over by holders.
- Your own page is the fastest fix. A current handle, a working domain and a named team on NAUT turn 4 raw fields into a record an investor can act on.
- Pull your own rowNAUT holds a follower count on 8,811 of 10,592 live company rows, with 178 carrying a handle trail.
- Date the numberIf your count was read on 30 May 2026, the number an investor sees is 5 months old.
- Explain the renameCaesar shows @telenomic dated 14 January 2025 and @caesar_data dated 10 May 2025.
- Point to one source of truthLink the domain from your X profile, as caesar.xyz is linked from x.com/caesar_data.
How to reach the teams behind a flagged handle
The snapshot tells you which rows need a human check. The NAUT page tells you who to ask. Each of the 11 projects named here has its own page carrying its team, its sector and its stored X handle, so a trail that looks odd takes 1 click to turn into a name: start with MemeCore at 8 handles, Sidekick and TaleX at 6, and Caesar for the worked example above. For a company with no team row on NAUT, the handle and the domain in the snapshot are the 2 doors worth knocking on, in that order.
Related reading on NAUT: Crypto project Twitter handle change: 3 checks, 10 flagged and Fake Twitter followers: 4 checks, 1 project, a 63.2x gap.
Can you pull this data through the NAUT API?
The company rows behind this article are the ones the projects endpoint returns, so GET https://api.naut.so/v1/projects/caesar returns the worked example above with its team, and GET https://api.naut.so/v1/projects?q=memecore finds a row by name before you pull it. A data call costs 5 credits, and the Essential plan at $49 a month carries 3,000 credits, so the full list of 11 projects named here is 11 calls; the parameters and prices are on https://naut.so/docs/api and https://naut.so/pricing. Verified Telegram, email and LinkedIn unlock on any paid NAUT plan, so you can start a 7-day trial and reveal the channels for the teams you want to reach.
NAUT X intel snapshot FAQ
What is an X intel snapshot on a NAUT company page?
It is the stored X account record on the row: the follower count, the timestamp that count was read, the trail of handles the account has used, and a paired set of flags carrying the token mint, the chain, the CTO marker and the account's token-post counts. Read on 11 November 2026, 8,811 of 10,592 live NAUT company rows carry a follower count and 178 carry a handle trail.
How current are NAUT's stored follower counts?
The follower checks on live rows run from 30 May 2026 to 6 November 2026, and 6,314 of the 8,811 stored counts carry a check timestamp. Quote the date beside the number: Arkham is 1,527,557 read on 30 May 2026.
How many crypto projects have changed their X handle?
Of the 178 live NAUT company rows carrying a handle trail on 11 November 2026, 89 hold 2 or more handles, and the longest trail on file is 8 handles at MemeCore. The trail is built from GMGN rename records tied to a Solana token mint, so it reaches token projects more often than other startups.
What does the CTO flag mean on a NAUT row?
CTO is a community takeover, which crypto.news defines as "When the holders of an abandoned token band together and run it themselves after the original developer walks away." 16 live NAUT company rows carry the flag, and none of the 10 longest handle trails is among them.
Where can I find the projects in this article and their contact channels?
All 11 projects named here have a NAUT page with their team, from MemeCore and Arkham to Caesar, and the same records come back through GET https://api.naut.so/v1/projects/caesar at 5 credits a call. Verified Telegram, email and LinkedIn unlock on any paid NAUT plan, so you can start a 7-day trial to open the channels on those pages.
Sources
- NAUT company records, read on 11 November 2026: 10,592 live rows, 8,811 follower counts, 6,314 check timestamps, 178 handle trails, 89 with 2 or more handles, 199 flag records, 16 with the CTO flag.
- Community takeover definition: crypto.news, read 30 June 2026.
- GMGN as a Solana token and X activity tracker: Medium write-up and GMGN's tracking post.
- Caesar's current handle and domain: x.com/caesar_data and caesar.xyz.
- Not read for this article: GMGN token pages and solscan.io token pages, both of which returned HTTP 403 to NAUT's fetch on 9 November 2026.