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 287–289 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Aug 2026, 08:18
288
no change
7 Aug 2026, 19:25
288
first reading
Engagement
20 posts held, back to 14 June 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
36.2%
avg views ÷ 288 subscribers
Avg views / post
104
4 posts measured
Reaction rate
5.11%
reactions ÷ views · ER floor
Posts in window
4
of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 4 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 29 July 2026
Posts held
20 (14 June 2026 – 29 July 2026)
Views total
417
Reactions total
18
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 08:18 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
51
Videos
4
Links
5
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. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
93 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 43.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
40
43.0%
🔥
24
25.8%
👀
7
7.53%
🫡
6
6.45%
💔
5
5.38%
👍
4
4.30%
✍
2
2.15%
🗿
2
2.15%
🌚
1
1.08%
😁
1
1.08%
🤔
1
1.08%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 17 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 93reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 June 2026 to 29 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Making money for the first time is one of the easiest things, especially when you're young and not mature enough to save it.
The hard part is keeping the money you made.
But the hardest part of all is making that money again after you've lost it.
Have a Good day
🚀 Big news — Birr Vault is here.
A year ago, my co-founder and I had one simple idea: trading USDT for Birr
on Telegram shouldn't be this messy, or this risky.
Nothing out there solved it the way we wanted. So we decided to build the
answer ourselves.
We've been designing, testing, and rebuilding Birr Vault from the ground up:
a secure peer-to-peer USDT ⇄ ETB exchange,
Today, that work is live. Anyone can buy or …
Hello, guys! 👋
How y'all doing?
Hope everyone's still alive.
I know I haven't been very consistent here. I wasn't really active, but it is what it is.
The important thing is... I'm back.
You know how fast time flies it wasn't easy to keep up. But now that I'm here, I'm looking forward to making the most of the rest of this summer.
We've still got half the summer ahead of us, and there's a lot coming your way.
S…
Fr, this man was a true legend.
They took a real legend way too soon man.... if the politics didn't cut his run short, there's no telling how far he would’ve taken this😭
Tbh, Colombia should've won that game fr. Them counters was nasty, and some of they players game vision was different. Only thing holdin' 'em back was they finishing
Portugal tho... I only watched the second half, but I ain't see them do nothin At least Leao was makin' runs, but for the GOAT, a 4.5 rating was generous ..
Showing the 12 most recent of 20 posts we hold for @FiraDFQ. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“ᴍᴀᴊᴏʀ ᴏɴᴇ” (@FiraDFQ), 288 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/FiraDFQ.
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.