Channel
@bulcoin_blc
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
295subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002324803743 |
|---|---|
| Type | Channel |
| Username | @bulcoin_blc |
| Description | First 100 -Pioneers stage 500 - Early Supporters 2000 -Contributers https://x.com/Bulcoin_BLC |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bulcoin_blc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 22:47 | 295 | no change |
| 6 Aug 2026, 17:34 | 295 | first reading |
20 posts held, back to 29 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 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 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (29 March 2026 – 5 August 2026) |
| Views total | 39 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 22:47 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.
Lifetime counters from Telegram’s own channel header, read 6 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.
13 reactions across 7 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 100.0% |
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 7 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 13reactions 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 29 March 2026 to 5 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.
Product Core: Three layers that do not mix The TON digital state is structured so that frequent actions (voting) are cheap, while rare actions (changing treasury rules) are controlled and transparent. 1. DAO Container Stores the state treasury, DAO parameters, and executes accepted decisions. This is the "constitution + treasury": voting results come in here, and payouts and setting changes go out. The chat admin c…
Blockchain contract for DAO on TON is completed The BulCoin team is conducting testing. You can join it earlier than others - by going through our referral program #DAO #ton #BulCoin FAQ | BUY
❤1
Design of the purchase process is ready The sequence looks like this: selection of goods payment confirmation holding of funds receiving access/file/delivery deal completion If something went wrong: • you can open a dispute • contact within the deal • attach materials The idea is to eliminate the situation when the money has been sent, and then everything is based only on trust. The application acts as a guarant…
Physical goods can be listed on the platform. The ads provide for: • photographs • characteristics • region • delivery options • condition of the goods • seller reviews Which means the following can be found in one application: — digital goods — services — physical goods Without division into separate services. #Ads #Goods #Marketplace FAQ | BUY
NFT Purchase Design Ready NFTs are separated into a unique type of product. The card provides: • attributes • characteristics • collection information • seller • history Our Marketplace will be the first where NFTs can be sold for your tokens, not just for Ton To make your token a part of our ecosystem - we will create a separate partner protocol for friendly tokens #NFT #Ton #Token #Marketplace FAQ | BUY
The market provides not only services. A separate category - digital goods: • accesses • accounts • files • keys • subscriptions • digital content The product card shows: - description - seller rating - reviews - statistics - purchase details After payment, the buyer gets access within the deal. Our app is the guarantor of the deal #Digital goods #Marketplace FAQ | BUY
Smart contracts for DAO and blockchain state are already ready and being tested If you understand how to test smart contracts, you can become our tester and give feedback. Smart contract here https://testnet.tonviewer.com/kQDW0KIZVe4OLC8Q1jtb_Zy8Gv0HiMND-zfp0_I1QA4T6Qol Want to know more about how voting in DAO will work? Put 🔥 #DAO #BulCoin #SmartContract #TON #Blockchain_State FAQ | BUY
Our designer has finished working on the deals screen. After creating an order, the work doesn't disappear in the correspondence. There are statuses: • new applications • execution • completed deals • dispute resolutions If a conflict arises: — the user can open a dispute — provide materials — track the resolution The history of actions is stored within the deal. The idea is simple: less chaos and more transpa…
Our team is developing a DAO on the Ton blockchain Upon completion, the DAO BulCoin will be launched and for our other partners Also, the launch of the Blockchain State is being prepared using the functionality of DAO NFT-passports Want more details? Hit 🔥 #DAO #Blockchain #Ton #Governance FAQ | BUY
We continue to showcase the BulCoin Market interface. In the third version of the app, a goods market will be launched. The designer has already finished working on the catalog screen and we are happy to show it to you What is already incorporated in the concept: • search for goods and services • filters and sorting • categories • separate tabs for your ads • quick transition to creating a task, resume, and produc…
❤2
Now is the best time to enter BLC Market. Early stage project: - actively forming structure - interfaces are being published - new mechanics are opening up If you're already here - you're getting in ahead of most. Scaling will follow next. #community #referrals FAQ | BUY
❤1
Invitation mechanics in BLC Market There will be a separate section in the app through which you can invite new users. This will allow: — community to grow faster — build connections between members — increase activity within the platform We will show the interface in the upcoming updates. #profile #community #referrals FAQ | BUY
❤1
Showing the 12 most recent of 20 posts we hold for @bulcoin_blc. 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 — 628,288 of 1,345,403entries 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 2 registered channels — 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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“BLC Market - mini-app BulCoin” (@bulcoin_blc), 295 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/bulcoin_blc.
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.