Channel
@OttoBSCDeployments
On this record: Growth · Engagement · Posts · Cite this entry
816subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001634412092 |
|---|---|
| Type | Channel |
| Username | @OttoBSCDeployments |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/OttoBSCDeployments |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 12:08 | 816 | -6 |
| 21 Aug 2026, 09:56 | 822 | -1 |
| 14 Aug 2026, 22:38 | 823 | -1 |
| 7 Aug 2026, 10:33 | 824 | no change |
| 7 Aug 2026, 10:23 | 824 | first reading |
20 posts held, back to 7 August 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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (7 August 2026 – 7 August 2026) |
| Views total | 65 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 10:33 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.
New BSC Token Deployment 🏷️ () 🔖 0x4EFc7130Bc6E34Fd454373E0C0818d731a0b2BFB Token Details: 🔗 Chain: BSC 📃 Contract: 0x4EFc...2BFB 🪙 Supply: 0 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x0f13c87d...39a8f432 🪪 Deployer Address: 0x1cf6...4329 💰 Deployer Balance: 0.0169 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ Mini Cat😂 (MC😂) 🔖 0xb52aB0411B23d343F616A75E899B20eF170A616a Token Details: 🔗 Chain: BSC 📃 Contract: 0xb52a...616a 🪙 Supply: 1000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xdaf685e1...8ab7d83a 🪪 Deployer Address: 0x7db0...a1de 💰 Deployer Balance: 50.0200 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ Pearl Nexus (PNX) 🔖 0x0Da1ba044739bb8C30336190031EA180D0EA3c29 Token Details: 🔗 Chain: BSC 📃 Contract: 0x0Da1...3c29 🪙 Supply: 100000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x912aa87f...ddc6cb87 🪪 Deployer Address: 0x5c29...5f55 💰 Deployer Balance: 9.4654 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ Blue Oasis (BOA) 🔖 0xed06Be0479F9eC4947A4563b88580E3c371a60Eb Token Details: 🔗 Chain: BSC 📃 Contract: 0xed06...60Eb 🪙 Supply: 200000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x19a91b20...7a655700 🪪 Deployer Address: 0x3aed...df82 💰 Deployer Balance: 0.1392 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ TGCC (TGCC) 🔖 0xd7d004611c86dD2988dC4C7e262eA35521DcBc1F Token Details: 🔗 Chain: BSC 📃 Contract: 0xd7d0...Bc1F 🪙 Supply: 21000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x30b8aa20...b49247cd 🪪 Deployer Address: 0xfaa9...95a9 💰 Deployer Balance: 0.3494 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ Nebula Cat (NEBCAT) 🔖 0xc0F2b0e86bf3D67cD02cEFE52CaC2fb37dBE6E8c Token Details: 🔗 Chain: BSC 📃 Contract: 0xc0F2...6E8c 🪙 Supply: 1000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x26c57eaf...3cbddbb1 🪪 Deployer Address: 0xe544...d7eb 💰 Deployer Balance: 1.3199 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ 香蕉币 (香蕉币) 🔖 0x274997963Fd732D52AEF623eb689031E0EEFeD88 Token Details: 🔗 Chain: BSC 📃 Contract: 0x2749...eD88 🪙 Supply: 9999 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x54ade232...bed96ddb 🪪 Deployer Address: 0x88cd...2c6b 💰 Deployer Balance: 0.0467 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ QQQB (QQQB) 🔖 0xC9892ec579C76BD241e4Ec39Dd4a802E2aA52F31 Token Details: 🔗 Chain: BSC 📃 Contract: 0xC989...2F31 🪙 Supply: 1000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xa3cac3c2...4bcc1df8 🪪 Deployer Address: 0x08e2...94ea 💰 Deployer Balance: 0.0010 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ 香蕉币 (香蕉币) 🔖 0x40417f565C2cc425Efe033347bC7A58DFaB75d6E Token Details: 🔗 Chain: BSC 📃 Contract: 0x4041...5d6E 🪙 Supply: 9999 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x6237ee29...287aa79d 🪪 Deployer Address: 0x88cd...2c6b 💰 Deployer Balance: 0.0469 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ AXIOS (AXS) 🔖 0xF8c85A02004163478196f0f11D8235236a7b7F02 Token Details: 🔗 Chain: BSC 📃 Contract: 0xF8c8...7F02 🪙 Supply: 100000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0x28ffdbd0...87acc2ef 🪪 Deployer Address: 0x47f0...6047 💰 Deployer Balance: 0.0339 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ 🌟币安暴富 (🌟币安暴富) 🔖 0xDD47E4DF3409d7644271Bc7212A3d706A91def35 Token Details: 🔗 Chain: BSC 📃 Contract: 0xDD47...ef35 🪙 Supply: 1000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xa80401fb...9c5fccc8 🪪 Deployer Address: 0xdc9d...a2e2 💰 Deployer Balance: 50.0200 BNB 🏦 Initial Funding: -
New BSC Token Deployment 🏷️ 夏天 (夏天) 🔖 0x38b4E858336ddEBcdeC538Ff09428Cf093a97777 Token Details: 🔗 Chain: BSC 📃 Contract: 0x38b4...7777 🪙 Supply: 1000000000 Token Checksums: ⏳ Deployer Details: 📡 Tx Hash: 0xc4d7c64f...1210a510 🪪 Deployer Address: 0x1c55...1d5d 💰 Deployer Balance: 2.9514 BNB 🏦 Initial Funding: -
Showing the 12 most recent of 20 posts we hold for @OttoBSCDeployments. 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Otto BSC Deployments” (@OttoBSCDeployments), 816 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/OttoBSCDeployments.
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.