Telegram RegisterThe public register of Telegram
Telegram profile photo for dTelecom

Channel

dTelecom

@dTelecomNetwork

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

34,844subscribers

-2,413 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001613824333
TypeChannel
Username@dTelecomNetwork
DescriptiondTelecom's official Telegram Channel ⚡️ TG Chat: @dtelecomchat Website: https://dtelecom.org Web3 Meeting App: https://dmeet.org Live-Streaming App: https://frogy.com Discord: https://discord.gg/dtelecom Twitter: https://x.com/dTelecom
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 October 2026
Measurements held35
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/dTelecomNetwork

Topic

Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

34,84437,25736,050.57 August 2026 — 37,257 subscribers7 August 2026 — 37,239 subscribers8 August 2026 — 37,199 subscribers9 August 2026 — 37,183 subscribers10 August 2026 — 37,137 subscribers11 August 2026 — 37,093 subscribers12 August 2026 — 37,057 subscribers13 August 2026 — 37,016 subscribers14 August 2026 — 36,969 subscribers16 August 2026 — 36,909 subscribers17 August 2026 — 36,849 subscribers18 August 2026 — 36,823 subscribers19 August 2026 — 36,765 subscribers20 August 2026 — 36,723 subscribers22 August 2026 — 36,658 subscribers23 August 2026 — 36,609 subscribers25 August 2026 — 36,531 subscribers26 August 2026 — 36,482 subscribers26 August 2026 — 36,446 subscribers27 August 2026 — 36,415 subscribers28 August 2026 — 36,381 subscribers29 August 2026 — 36,344 subscribers30 August 2026 — 36,330 subscribers31 August 2026 — 36,291 subscribers1 September 2026 — 36,239 subscribers3 September 2026 — 36,203 subscribers4 September 2026 — 36,132 subscribers7 September 2026 — 36,028 subscribers10 September 2026 — 35,906 subscribers12 September 2026 — 35,847 subscribers14 September 2026 — 35,794 subscribers15 September 2026 — 35,746 subscribers18 September 2026 — 35,678 subscribers30 September 2026 — 35,198 subscribers5 October 2026 — 34,844 subscribers7 August 20265 October 2026
35 measurements spanning 59 days, net -2,413. 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 34,482–37,619 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
5 Oct 2026, 19:3734,844-354
30 Sept 2026, 09:2035,198-480
18 Sept 2026, 01:1935,678-68
15 Sept 2026, 18:3735,746-48
14 Sept 2026, 05:3935,794-53
12 Sept 2026, 11:5835,847-59
10 Sept 2026, 12:0235,906-122
7 Sept 2026, 08:1936,028-104
4 Sept 2026, 12:1736,132-71
3 Sept 2026, 00:2636,203-36
1 Sept 2026, 21:2336,239-52
31 Aug 2026, 18:2536,291-39
30 Aug 2026, 17:1236,330-14
29 Aug 2026, 20:4436,344-37
28 Aug 2026, 20:5736,381-34
27 Aug 2026, 23:4736,415-31
26 Aug 2026, 22:1436,446-36
26 Aug 2026, 00:5336,482-49
25 Aug 2026, 00:5336,531-78
23 Aug 2026, 14:4536,609first reading

Engagement

21 posts held, back to 11 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 108 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.39%
avg views ÷ 34,844 subscribers
Avg views / post
1,530
1 post measured
Reaction rate
1.90%
reactions ÷ views · ER floor
Posts in window
1
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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 September 2026
Posts held21 (11 December 2025 – 30 September 2026)
Views total1,530
Reactions total29
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Oct 2026, 07:04 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
95
Videos
34
Links
111

Lifetime counters from Telegram’s own channel header, read 7 October 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.

Video runtime
48s
Average length
24s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

6,989 reactions across 21 posts, in 4 distinct kinds. The most used accounts for 73.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5,13673.5%
👍1,26518.1%
🎉3404.86%
👏2483.55%

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 21 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 6,989 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 11 December 2025 to 30 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.

Telegram Stars

Stars received
100
across the posts below
Posts paid on
14
of 21 we hold a reading for · 67%
Most on one post
28
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dTelecomNetwork. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 21 most recent posts we hold for this entry, published 11 December 2025 to 30 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

30 Sept 2026, 13:01 UTC≈1,530 views29 reactions4 Starsread 7 October 2026
Photo

🔴 Meeting recording is now live in dMeet Record your group meetings and keep them where the rest of your meeting already lives. ▪️ Start recording in any group meeting ▪️ Watch the replay right in the app - iOS, Android or web ▪️ Download the file when you have permission ▪️ Saved to your meeting history, next to your AI summaries The summary tells you what was decided. The recording takes you back to the moment i…

❤25🎉4

20 Jul 2026, 18:30 UTC≈4,170 views57 reactions1 Starread 7 October 2026
Photo

🚀 Big dMeet update: Team Workspaces are live Your company now gets a shared AI Memory built from its own meetings. • Persistent rooms for every team (Marketing, Sales, Product...) • Shared meeting history with summaries, decisions, action items • Ask questions across all meetings - ChatGPT-style, with answers linked to the source • Roles, shared AI credits, one subscription for the whole team The more meetings you…

❤55👍2

2 Mar 2026, 15:08 UTC≈18,500 views1,188 reactions14 Starsread 7 October 2026
Video

Earlier we outlined our integration of x402. Here’s how it will express in dMeet. Real-time translation runs as audio flows through STT, is translated, converted back via TTS, and streamed to the listener. Instead of locking this behind subscriptions or fixed plans, each session (or minute) can be priced dynamically. If payment is required: х402 with the price ➡️ programmatic pay ➡️ continue the call. Usage-based…

❤844👍236👏62🎉46

26 Feb 2026, 10:55 UTC≈17,100 views488 reactionsread 7 October 2026
Video

Legacy infra is about human <> human Today's reality is human <> agent Real-time infra is not just about: - Voice - Video - Routing It's also about: ✅ Edge AI ✅ STT (speech-to-text) ✅ TTS (text-to-speech) ✅ x402 payments ✅ Cost efficient latency Same thesis. Bigger surface area. Voice AI — already available via API/SDK.

❤368🎉64👍55👏1

19 Feb 2026, 16:24 UTC≈33,700 views1,240 reactions9 Starsread 7 October 2026
Photo

FROGY 👉 Invisible Web3 Adoption - Viewers join from mobile - Top up via Apple/Google Pay - Donate like they always do Under the hood: - USDC on Solana - On-chain rewards - Ownership logic 😌 Web2 UX 😎 Web3 rails Join real adoption 👇 Earn portion of $2.6M airdrop

❤926👍249🎉65

18 Feb 2026, 15:42 UTC≈24,800 views285 reactions1 Starread 7 October 2026
Video

FROGY_LIVE is a next-gen live-streaming on Solana On Feb alone: 🔸 9K+ unique Web2 viewers 🔸 10+ min average session duration Web2 streamers Web2 audience Usage and Revenue - first. Runs on dTelecom rails.

❤226👍59

16 Feb 2026, 13:12 UTC≈15,200 views526 reactions1 Starread 7 October 2026
Photo

Creator economy didn’t fail. Infra running it did. FROGY fixes it: 🔸 90% revshare with creators 🔸 Instant USDC payouts 🔸 Web2 UX on Web3 rails No platform tax. No 30-day waits. No crypto friction. Next-gen live-streaming on Solana Powered by dTelecom Stream. Earn. Own.

❤368👏96👍62

11 Feb 2026, 16:21 UTC≈20,300 views1,558 reactions10 Starsread 7 October 2026
Photo

Voice AI: $2.4B → $47B (by 2034) So we shipped the rails. First x402 real-time STT: 🔸 AI agent → pays in USDC → gets live transcription 🔸 $0.005/min. No API 🔸 Cheaper then OpenAI ($0.006), Deepgram ($0.0077), Google ($0.016), Azure ($0.017), AWS ($0.024). 🤖-to-🤖 commerce is LIVE Thanks to Father of AGI - Benjamin Goertzel - for inspiration and validation.

❤1,150👍295🎉85👏28

10 Feb 2026, 15:06 UTC≈15,600 views1,093 reactions28 Starsread 7 October 2026
Video

The $3.5T telecom industry is being rebuilt on-chain ⛓️ dTelecom is the default DePIN layer for real-time voice, video, and AI. 🔸Backed by: - Solana Foundation - Google - peaq - ElevenLabs 🔸Traction: 50K+ users 35M+ mins processed The $2.6M Airdrop is now LIVE 👉 Join: http://rewards.dtelecom.org

❤809👍208🎉55👏21

5 Feb 2026, 16:05 UTC≈10,400 views139 reactions2 Starsread 7 October 2026
Photo

dTelecom Startup Grants are LIVE 🔥 dTelecom Startup Grants = production-grade real-time infra, free for 6 months. 1️⃣ What selected teams get • 6 months of dTelecom Plus (≈ $9,240 value) • Unlimited voice & video minutes • AI-native features: transcription, translation, agent-ready SDKs • Up to 1 Gbps throughput (real traffic, real load) • Access to decentralized real-time network (dRTC) • Direct access to dTeleco…

❤118👍21

4 Feb 2026, 19:14 UTC≈5,630 views82 reactionsread 7 October 2026
Photo

"Hype fades. Infrastructure compounds" Fresh article from dTelecom CEO Petr Malyukov breaking down why real infra is where long-term value is built once the FOMO is gone. 🔸From narratives → fundamentals 🔸From speculation → execution 🔸From trending → what actually scales Published by Saudi Moments - one of the leading publishers in MENA (also behind INC Arabia). Read it here 👇 https://saudimoments.com/beyond-tech…

❤51🎉16👍14👏1

20 Jan 2026, 14:23 UTC≈3,580 views43 reactionsread 7 October 2026
Video

Enterprise outages now cost $14,056 per minute 😱 Not because systems fully go down, but because teams spend 20–40% of that time just figuring out who’s affected. 👉 That’s $2,800–$5,600 wasted every minute. 👉 Over a 4-hour incident: $750K–$1.5M burned. Now you know, why web2 “trust us” doesn’t scale any more. In real-time infra things like 🔸 visibility 🔸 verifiability 🔸 control aren’t nice-to-haves they’re cost co…

❤34👍9

Showing the 12 most recent of 21 posts we hold for @dTelecomNetwork. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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 5 October 2026 — this entry's latest reading, not the date you are reading this.

“dTelecom” (@dTelecomNetwork), 34,844 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/dTelecomNetwork.

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.