Telegram RegisterThe public register of Telegram
Telegram profile photo for dabbackwood

Channel

dabbackwood

@dabackwood

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

958subscribers

+112 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003847888027
TypeChannel
Username@dabackwood
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live21 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/dabackwood

Growth

84695890212 August 2026 — 846 subscribers12 August 2026 — 846 subscribers13 August 2026 — 853 subscribers21 August 2026 — 958 subscribers12 August 202621 August 2026
4 measurements spanning 8 days, net +112. 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 829–975 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 03:51958+105
13 Aug 2026, 14:29853+7
12 Aug 2026, 17:45846no change
12 Aug 2026, 17:33846first reading

Engagement

20 posts held, back to 29 July 2026the 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
74.6%
avg views ÷ 958 subscribers
Avg views / post
715
19 posts measured
Reaction rate
3.75%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 18 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held20 (29 July 202612 August 2026)
Views total13,582
Reactions total484
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 17:45 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

Video runtime
16s
Average length
16s

Measured directly from 1 video 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

484 reactions across 18 posts, in 10 distinct kinds. The most used accounts for 33.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 532809288129711460016433.9%
custom 532798663239614649810822.3%
😈5010.3%
custom 5328072553216902722489.92%
custom 5328141259808736042347.02%
custom 5327948252568389038285.79%
custom 5328166522806371171173.51%
custom 5327947573963555959163.31%
custom 5327863353949849624142.89%
custom 532783353828688033151.03%

Custom emoji. 9 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 18 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 484reactions 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 July 2026 to 12 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.

Telegram Stars

Stars received
32
across the posts below
Posts paid on
6
of 19 we hold a reading for · 32%
Most on one post
20
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dabackwood. 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 20 most recent posts we hold for this entry, published 29 July 2026 to 12 August 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

12 Aug 2026, 16:11 UTC121 views13 reactionsread 12 August 2026

покупаем

custom 53280928812971146007custom 53279866323961464984custom 53280725532169027222

12 Aug 2026, 16:11 UTC121 views5 reactionsread 12 August 2026
Photo

Photo, posted without a caption

custom 53280725532169027223custom 53279866323961464981custom 53281412598087360421

10 Aug 2026, 11:47 UTC427 views18 reactionsread 12 August 2026
File

@dabackwood

custom 53281665228063711718custom 53280725532169027225custom 53279482525683890382custom 53281412598087360422custom 53279866323961464981

8 Aug 2026, 13:01 UTC641 views24 reactionsread 12 August 2026

Posted without readable text

custom 532809288129711460013custom 53279475739635559596custom 53278335382868803315

8 Aug 2026, 09:59 UTC649 views17 reactions20 Starsread 12 August 2026

ещё на 1000 подписчиков будет розыгрыш ❤️

custom 532809288129711460017

7 Aug 2026, 16:55 UTC697 views18 reactionsread 12 August 2026
File

@dabackwood

😈8custom 53280725532169027225custom 53280928812971146005

7 Aug 2026, 10:30 UTC727 views78 reactions2 Starsread 12 August 2026

Posted without readable text

custom 532798663239614649841custom 532809288129711460015😈8custom 53278633539498496244custom 53279482525683890384custom 53279475739635559593custom 53281412598087360423

7 Aug 2026, 10:18 UTC681 viewsread 12 August 2026

все же набирали, вечером розыгрыш

7 Aug 2026, 06:02 UTC758 views36 reactionsread 12 August 2026
File

@dabackwood

custom 532807255321690272222custom 53280928812971146005custom 53281665228063711714custom 53279482525683890383custom 53278633539498496242

7 Aug 2026, 05:57 UTC688 views8 reactionsread 12 August 2026
File

@dabackwood

custom 53281412598087360427custom 53281665228063711711

6 Aug 2026, 06:03 UTC747 views30 reactionsread 12 August 2026
Video

барни меня ложат в больницу с сильным повреждением ноги, что мне кидает кент в поддержку

custom 532798663239614649819custom 53281412598087360426custom 53280928812971146003custom 53280725532169027222

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

Citation-graph rank

Citation-graph rank — 406,993 of 1,620,455entries 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.

Mentions

Named by 3 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.

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.

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

“dabbackwood” (@dabackwood), 958 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/dabackwood.

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.