3 measurements spanning 3 days, net +4. 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 1,031–1,037 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 14:17
1,036
+4
8 Aug 2026, 00:21
1,032
no change
7 Aug 2026, 15:48
1,032
first reading
Engagement
14 posts held, back to 12 March 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
99.6%
avg views ÷ 1,036 subscribers
Avg views / post
1,030
3 posts measured
Reaction rate
2.39%
reactions ÷ views · ER floor
Posts in window
3
of 14 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
14 (12 March 2026 – 6 August 2026)
Views total
3,095
Reactions total
74
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 00:21 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.
Reaction mix
510 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 44.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
229
44.9%
❤
152
29.8%
👍
72
14.1%
😱
55
10.8%
😨
2
0.392%
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 14 of the 14 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 510reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 12 March 2026 to 6 August 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.
All nnchan.ru domains (nnp, nnm, mp, mp2) will soon stop working.
So make sure you have changed URLs, settings, bookmarks, etc. to nnproject.cc
nnp.nnchan.ru -> nnproject.cc
mp.nnchan.ru -> mp.nnproject.cc
mp2.nnchan.ru -> mp2.nnproject.cc
nnm.nnchan.ru -> f.nnproject.cc
Java volume controls patch for S60 3rd Edition FP1 (Symbian 9.2).
Enables volume control with media keys for MIDI sounds, combined with performance patch.
Tested on Nokia E90, E71, N95, N82, E51
Download: https://nnproject.cc/jvms60v31
Donate: https://boosty.to/nnproject/donate
Java performance patch for Nokia E6
Doubles maximum FPS on Canvas by disabling slow hardware "acceleration".
Download: https://nnproject.cc/e6javapatch
Donate: https://boosty.to/nnproject/donate
1080p playback support patch for Belle FP1/FP2.
This is a port of hardware decoding driver from Nokia 808 that adds H.264 Level 4.0 support.
Tested on Nokia 701 with FP2, and 700 with FP1, should be compatible with 603 as well.
Download: https://nnproject.cc/belle1080p
Donate: https://boosty.to/nnproject/donate
Belle HTTPS Streaming patch.
Enables online playback with HTTPS protocol in system player on Belle Refresh, FP1, FP2.
Download: https://nnproject.cc/bellehttpsplayer
Donate: https://boosty.to/nnproject/donate
KEmulator nnmod v2.21.4
Features:
- Implemented VolumeControl in MIDI player
- Implemented arrays view in Class Watcher
Updates:
- Improved MIDI playback on default JRE synthesizer
- Improved VLC player
- Improved LCDUI layout
Fixes:
- Fixed CORS headers not working in HttpConnection (#325)
- Fixed freeze on startup when MemoryView is enabled (#321)
- Fixed M3G ambient light
- Fixed volume control on Linux
- Fixed…
TLS 1.2 patch for Symbian Qt has been updated with simplified installation process.
Updated guide for Symbian Anna, Belle devices
c2z4bin patch and DomainSrv are no longer required
Download: https://nnproject.cc/qtls
👍13
Showing the 12 most recent of 14 posts we hold for @nnmidlets. 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
Citation-graph rank — 435,513 of 1,160,990entries 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.
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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“nnproject MIDlets” (@nnmidlets), 1,036 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/nnmidlets.
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.