NBIT | NEWS π pinned Β«NBITEX dev update β We are currently testing cryptocurrency deposit/withdrawal and spot trading features on the NBITEX exchange. They are set to launch soon, so stay tuned to ensure you don't miss out!Β»

Channel
NBIT | NEWS π
@notbitco_in
On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Citations Β· Telegram's recommendations Β· Cite this entry
21,534subscribers
-1,159 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 10,000β31,623.
Register entry
| Telegram ID | -1002028234738 |
|---|---|
| Type | Channel |
| Username | @notbitco_in |
| Created | Between 1 November 2023 and 31 May 2024 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/notbitco_in |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 09:59 | 21,534 | -51 |
| 15 Sept 2026, 07:39 | 21,585 | -38 |
| 13 Sept 2026, 12:59 | 21,623 | -37 |
| 11 Sept 2026, 20:38 | 21,660 | -66 |
| 9 Sept 2026, 08:17 | 21,726 | -89 |
| 6 Sept 2026, 00:56 | 21,815 | -66 |
| 3 Sept 2026, 20:38 | 21,881 | -26 |
| 2 Sept 2026, 09:26 | 21,907 | -22 |
| 1 Sept 2026, 10:59 | 21,929 | -40 |
| 31 Aug 2026, 08:32 | 21,969 | -32 |
| 30 Aug 2026, 05:19 | 22,001 | -16 |
| 29 Aug 2026, 04:33 | 22,017 | -22 |
| 28 Aug 2026, 07:28 | 22,039 | -15 |
| 27 Aug 2026, 04:04 | 22,054 | -24 |
| 26 Aug 2026, 03:45 | 22,078 | -19 |
| 25 Aug 2026, 06:27 | 22,097 | -33 |
| 24 Aug 2026, 06:32 | 22,130 | -45 |
| 22 Aug 2026, 15:22 | 22,175 | -33 |
| 21 Aug 2026, 06:43 | 22,208 | -16 |
| 20 Aug 2026, 10:02 | 22,224 | first reading |
Engagement
21 posts held, back to 20 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 57 pages of Telegramβs post history, 20 posts per page.
- ERR Β· 30 days
- 0.659%
- avg views Γ· 21,534 subscribers
- Avg views / post
- 142
- 1 post measured
- Reaction rate
- 13.4%
- reactions Γ· views Β· ER floor
- Posts in window
- 2
- of 21 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.
| Window | Rolling 30 days Β· latest post in window 3 September 2026 |
|---|---|
| Posts held | 21 (20 March 2026 β 3 September 2026) |
| Views total | 142 |
| Reactions total | 19 |
| Forwards / comments | not exposed by the public surface β not measured, not estimated |
| Readings taken | 3 Sept 2026, 13:20 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
662 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 28.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| β€ | 190 | 28.7% | |
| π₯ | 187 | 28.2% | |
| π | 162 | 24.5% | |
| π | 58 | 8.76% | |
| π€£ | 15 | 2.27% | |
| π | 8 | 1.21% | |
| π₯° | 8 | 1.21% | |
| π³ | 6 | 0.906% | |
| π | 6 | 0.906% | |
| π― | 5 | 0.755% | |
| π | 5 | 0.755% | |
| π₯΄ | 4 | 0.604% | |
| π’ | 3 | 0.453% | |
| πΎ | 2 | 0.302% | |
| π€‘ | 2 | 0.302% | |
| π | 1 | 0.151% |
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 20 of the 21 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 662 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 21 most recent posts we hold, published 20 March 2026 to 3 September 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.
Recent posts
NBITEX dev update β We are currently testing cryptocurrency deposit/withdrawal and spot trading features on the NBITEX exchange. They are set to launch soon, so stay tuned to ensure you don't miss out!
π9π₯9π1
Let's use REFILL WITH POINTS method to recharge energy! REMEMBER: Chatting in group to recharge energy is disabled! (only open in some events) Open app
π19π₯6π4
π§ nbitchain dev update Just shipped 3 perf optimization phases on our Rust blockchain for AI compute: Phase A β RocksDB WriteBatch (atomic flush per block) Phase B β Sealevel-style parallel tx execution Phase C β TPU inter-block pipeline (sig verify overlaps state execution) Results: 92.2k TPS peak Β· 5.9Γ vs baseline The pipeline alone adds 2.8Γ by hiding Ed25519 sig verify latency behind state execution of the pβ¦
π₯17π12β€7
Now you can refill energy any time by the option "Refill with point" base cost is 100 point Explore now
π20π₯11β€4π3π€‘2
π CHANGE POOL COST UPDATE Hey NBIT miners ! π We've updated the Pool Change cost to scale with how many times you switch per day: β’ 1st: 500 points β’ 2nd: 1,000 pts β’ 3rd: 2,000 pts β’ 4th: 3,500 pts β’ 5th: 5,000 pts β’ 6th+: 8,000 pts The counter resets every day, so costs return to 500 pts the next day. Why? The more you mine, the more you pay β just like in the real world. Thanks for your support! π
π19π5π₯΄4β€3π₯1
Early benchmark results are in. The numbers aren't our destination they're our starting point. The core systems are working, and optimization is already underway. #nbitchain #layer1 #nbit #notbitcoin #nbitex #blockchain
π17β€9π₯7π3
Stay up-to-date with the latest world news concisely through NBNET Newsπ nbitex.notbitco.in/nbnet/news
β€14π₯8π4π2
π Result event "CELEBRATING THE LAUNCH OF NBNET SOCIAL" π 1st : 50,000 NBIT : 5351469400- TELE ID π₯ 2nd : 30,000 NBIT: 6408746322- TELE ID π₯ 3rd : 20,000 NBIT: 2220472579 - NBITEXID (Need send TelegramId to admin to receive the reward) π 4th : 10,000 NBIT :5069473940- TELE ID π 5th : 5,000 NBIT :1457170504- TELE ID
β€12π6π1
Now, you can setting background themes on NBNET
π10β€8π€£6π₯3
The easy way to install NBITEX App for both Android and iOS. Open nbitex.notbitco.in on your browser, click More on the menu => Install app Or direct to the link https://nbitex.notbitco.in/install
π₯10π4π1
Most exchanges show charts. We show the future. Enter the terminal: https://nbitex.notbitco.in #nbitex #nbitex_terminal #exchange
β€19π7π₯5π―1π€£1
Showing the 12 most recent of 21 posts we hold for @notbitco_in. 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.
Mentions
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.
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.
Appears in Telegramβs recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly β each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone elseβs query is independent of having been queried itself.
@airdrop_alert_dot_com Β· 194,993
Telegram ranks this channel #79 of 90 here β alongside 89 others β read 20 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegramβs list for THAT channel, not this one β see how this is measured.
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 17 September 2026 β this entry's latest reading, not the date you are reading this.
βNBIT | NEWS πβ (@notbitco_in), 21,534 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/notbitco_in.
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.