Telegram RegisterThe public register of Telegram
Telegram profile photo for FIRE KR

Channel

FIRE KR

@ROKMCFIREANT

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

59subscribers

-7 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-1002730334410
TypeChannel
Username@ROKMCFIREANT
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live2 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/ROKMCFIREANT

Topic

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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.

Growth

596662.57 August 2026 — 66 subscribers10 August 2026 — 66 subscribers16 August 2026 — 64 subscribers24 August 2026 — 63 subscribers10 September 2026 — 62 subscribers18 September 2026 — 63 subscribers2 October 2026 — 59 subscribers7 August 20262 October 2026
7 measurements spanning 55 days, net -7. 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 58–67 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 00:4059-4
18 Sept 2026, 02:5963+1
10 Sept 2026, 18:2162-1
24 Aug 2026, 21:4963-1
16 Aug 2026, 08:1464-2
10 Aug 2026, 02:0166no change
7 Aug 2026, 23:1766first reading

Engagement

20 posts held, back to 16 January 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 26 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
25s
Average length
25s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

26 Jul 2026, 07:21 UTC9 viewsread 10 August 2026
Forwarded from @ahboyashreads

List of crypto project shutdowns in 2026 a) CEX • BitMEX • BitMart • AscendEx b) DeFi • Zapper • Odos Protocol • Radiant Protocol • Satori Finance • http://Summer.fi • Goldfinch • Step Finance • Dango Exchange • Rage Trade • MilkyWay • Angle Protocol • Ranger Finance c) Infra • Lamina1 • Loopring • Botanix • Polygon zkEVM • Leap Wallet • Tally • Parsec • Lattice / Redstone

26 Jul 2026, 02:55 UTC8 viewsread 10 August 2026
Forwarded from @followin_ko

BWENEWS 뉴스, 비트마트(BitMart) 거래소, 운영 중단 발표 —🔗link

16 Jul 2026, 03:35 UTC18 viewsread 10 August 2026
Forwarded from @minchoisfuturePhoto

Cascade 근황 (비관적) 팀은 여전히 완전히 침묵중 방금 볼트에서 큰 돈이 빠져나온 후 DAI로 스왑 자세한 내용은 궈니님의 포스팅 참고 https://x.com/0xGwoni/status/2077569101413974512

8 Jul 2026, 06:00 UTC23 viewsread 10 August 2026
Forwarded from @krw_pricePhoto

🔴 ₩1,505.00 @KRW_Price 📊 More: @MorePrices

Showing the 12 most recent of 20 posts we hold for @ROKMCFIREANT. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

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 2 October 2026 — this entry's latest reading, not the date you are reading this.

“FIRE KR” (@ROKMCFIREANT), 59 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/ROKMCFIREANT.

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.