Telegram RegisterThe public register of Telegram
Telegram profile photo for Etherscan Tracker - ERC404

Channel

Etherscan Tracker - ERC404

@EtherscanTrackerERC404

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

207subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002095895737
TypeChannel
Username@EtherscanTrackerERC404
DescriptionPowered by @etherscan_tracker
CreatedBetween 1 November 2023 and 2 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/EtherscanTrackerERC404

Growth

2077 Aug 2026, 12:07 — 207 subscribers8 Aug 2026, 11:05 — 207 subscribers7 Aug 2026, 12:078 Aug 2026, 11:05
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 206–208 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 11:05207no change
7 Aug 2026, 12:07207first reading

Engagement

20 posts held, back to 2 April 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 November 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1,310

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

12 Nov 2024, 05:12 UTC73 viewsread 8 August 2026

🔍 Found new ERC404 | 0x60F3B6814dec984346e347109DBBE4c9Ee5f42d0 Total Supply: 0 Deployer (🏦 Balance: 0.393 ETH) Trade/Snipe: Banana | Magnum | Starbot

11 Nov 2024, 09:51 UTC74 viewsread 8 August 2026

🔍 Found new ERC404 | 0xEA915aa390048148df8f6aFcbd40B8f927a2fAf4 Total Supply: 0 Deployer (🏦 Balance: 0.514 ETH) Trade/Snipe: Banana | Magnum | Starbot

11 Nov 2024, 04:44 UTC75 viewsread 8 August 2026

🔍 Found new ERC404 | 0x9f4a9Ef56B164Da0BF06218030c7C16D592Cedcc Total Supply: 0 Deployer (🏦 Balance: 0.202 ETH) Trade/Snipe: Banana | Magnum | Starbot

4 Nov 2024, 08:50 UTC75 viewsread 8 August 2026

🔍 Found new ERC404 | 0x9B55D0e0029F2c732a49607Ab551fE27541cD7Fb Total Supply: 0 Deployer (🏦 Balance: 0.023 ETH) Trade/Snipe: Banana | Magnum | Starbot

1 Nov 2024, 02:54 UTC67 viewsread 8 August 2026

🔍 Found new ERC404 | 0x8DaaebB56a513BF51b87749A69f8a9FE8c5A34f7 Total Supply: 0 Deployer (🏦 Balance: 0.039 ETH) Trade/Snipe: Banana | Magnum | Starbot

31 Oct 2024, 07:49 UTC57 viewsread 8 August 2026

🔍 Found new ERC404 | 0x84E5E9bF7B6fa562E32B2A4ed2bCa59d9dfB8401 Total Supply: 0 Deployer (🏦 Balance: 0.184 ETH) Trade/Snipe: Banana | Magnum | Starbot

29 Oct 2024, 17:13 UTC50 viewsread 8 August 2026

🔍 Found new ERC404 | Circle 0x96dfE5e42026eD3629fCB2A09C7B4eeEB38fb5F6 Total Supply: 1 Deployer (🏦 Balance: 0.120 ETH) Trade/Snipe: Banana | Magnum | Starbot

29 Oct 2024, 16:51 UTC46 viewsread 8 August 2026

🔍 Found new ERC404 | Circle 0xA662a802fddd8DcA7EfC2980CCc65F12d3255750 Total Supply: 1 Deployer (🏦 Balance: 0.157 ETH) Trade/Snipe: Banana | Magnum | Starbot

29 Oct 2024, 16:21 UTC43 viewsread 8 August 2026

🔍 Found new ERC404 | Circle 0xd50Ba1a4Ddd01281162c5502688Fc5A64E9Ac6D9 Total Supply: 1 Deployer (🏦 Balance: 0.189 ETH) Trade/Snipe: Banana | Magnum | Starbot

24 Oct 2024, 14:10 UTC49 viewsread 8 August 2026

🔍 Found new ERC404 | Square 0x038e902832ECFf6b288595ea09D17947d67B0461 Total Supply: 1 Deployer (🏦 Balance: 0.542 ETH) Trade/Snipe: Banana | Magnum | Starbot

19 Oct 2024, 08:16 UTC54 viewsread 8 August 2026

🔍 Found new ERC404 | 0x37e88B022a14cfbA14Cd46ee268ce6eA0f5f597C Total Supply: 0 Deployer (🏦 Balance: 0.127 ETH) Trade/Snipe: Banana | Magnum | Starbot

Showing the 12 most recent of 20 posts we hold for @EtherscanTrackerERC404. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Etherscan Tracker - ERC404” (@EtherscanTrackerERC404), 207 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/EtherscanTrackerERC404.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.