Channel
@republic_updates
On this record: Topic · Growth · Engagement · Posts · Cite this entry
85subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003345304584 |
|---|---|
| Type | Channel |
| Username | @republic_updates |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/republic_updates |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 27 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 09:35 | 85 | -1 |
| 18 Sept 2026, 07:21 | 86 | -1 |
| 10 Sept 2026, 00:57 | 87 | -2 |
| 16 Aug 2026, 05:37 | 89 | -1 |
| 9 Aug 2026, 14:33 | 90 | no change |
| 7 Aug 2026, 17:52 | 90 | first reading |
20 posts held, back to 8 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.
☎️ 24h leaderboard update Big jumps: $BUDDY: 9 → 5 $ARTSIV: 22 → 14 $YODA: 10 → 7 $jMOEW: 27 → 21 $POK: 21 → 17 $FPIBANK: 24 → 20 $PLANE: 19 → 16 $DOGS: 7 → 6 $ANON: 28 → 24 $ROSE: 35 → 32 $DUREV: 12 → 11 $TONSKI: 31 → 29 Losing momentum: $AMORE: 5 → 9 $FRT: 6 → 10 $VILARSO: 18 → 27 $Teleclaw: 16 → 22 $MITTENS: 14 → 19 $KGO: 20 → 23 $REGI: 25 → 28 $PLUSHPEPE: 11 → 12 $FRE: 23 → 25 $BYC: 17 → 18 New tokens added: $…
$UTYA liquidity: +$5.8k @ MCAP: $35.3M / 5m
$UTYA liquidity: +$9.4k @ MCAP: $35.3M / 5m
$ANON liquidity: -$5.7k @ MCAP: $385.4k / 5m
$REDO liquidity: -$14.6k @ MCAP: $7.2M / 5m
$MITTENS price: -12% @ MCAP: $181.6k / 5m
$UTYA liquidity: +$7.6k @ MCAP: $34.9M / 5m
$UTYA liquidity: +$7.3k @ MCAP: $34.4M / 5m
$UTYA liquidity: -$6.0k @ MCAP: $34M / 5m
$FRT liquidity: -$6.9k @ MCAP: $7.4M / 5m
$UTYA liquidity: +$6.3k @ MCAP: $34.2M / 5m
$UTYA liquidity: -$5.1k @ MCAP: $34M / 5m
Showing the 12 most recent of 20 posts we hold for @republic_updates. 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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“Meme Republic Updates” (@republic_updates), 85 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/republic_updates.
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.