Channel
@UniRocket_FLOKI
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
43subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001651979064 |
|---|---|
| Type | Channel |
| Username | @UniRocket_FLOKI |
| Description | created by @paxwion |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/UniRocket_FLOKI |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 16:31 | 43 | no change |
| 6 Aug 2026, 22:45 | 43 | first reading |
20 posts held, back to 2 August 2023 — 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 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 18 February 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
👹 Sold 1504300000 Shiba Floki Inu for 0.00037306 BNB on PancakeSwap 🔴 1 Shiba Floki Inu = $0.000000000059519 MC: $59.52K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
👹 Sold 213630000000 Shiba Floki Inu for 0.053042 BNB on PancakeSwap 🔴 1 Shiba Floki Inu = $0.000000000059589 MC: $59.59K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
🚀 Bought 340000000000 Shiba Floki Inu for 0.084807 BNB on PancakeSwap 🟢 1 Shiba Floki Inu = $0.000000000060113 MC: $60.11K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
🚀 Bought 428080000000 Shiba Floki Inu for 0.1065 BNB on PancakeSwap 🟢 1 Shiba Floki Inu = $0.000000000059708 MC: $59.71K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
👹 Sold 224330000000 Shiba Floki Inu for 0.055496 BNB on PancakeSwap 🔴 1 Shiba Floki Inu = $0.000000000059620 MC: $59.62K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
🚀 Bought 100310000000 Shiba Floki Inu for 0.025 BNB on PancakeSwap 🟢 1 Shiba Floki Inu = $0.000000000059565 MC: $59.56K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
🚀 Bought 71271000000 Shiba Floki Inu for 0.017752 BNB on PancakeSwap 🟢 1 Shiba Floki Inu = $0.000000000059530 MC: $59.53K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
🚀 Bought 1681500000000 Shiba Floki Inu for 0.41639 BNB on PancakeSwap 🟢🟢🟢 1 Shiba Floki Inu = $0.000000000059184 MC: $59.18K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
🚀 Bought 1699900000000 Shiba Floki Inu for 0.41624 BNB on PancakeSwap 🟢🟢🟢 1 Shiba Floki Inu = $0.000000000058522 MC: $58.52K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
🚀 Bought 824730000000 Shiba Floki Inu for 0.20026 BNB on PancakeSwap 🟢 1 Shiba Floki Inu = $0.000000000058277 MC: $58.28K 🥞 Buy | 📶 Tx | 📈 Chart 🚀 @UniRocket_Listings
Showing the 12 most recent of 20 posts we hold for @UniRocket_FLOKI. 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.
Citation-graph rank — 932,335 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“UniRocket FLOKI” (@UniRocket_FLOKI), 43 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/UniRocket_FLOKI.
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.