Channel
@dogsl1fe
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry
85,203subscribers
+28 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001273867200 |
|---|---|
| Type | Channel |
| Username | @dogsl1fe |
| Description | Номер заявления РКН: 7706831491 |
| Created | 8 November 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/dogsl1fe |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:32 | 85,203 | -28 |
| 11 Aug 2026, 08:23 | 85,231 | -5 |
| 10 Aug 2026, 10:32 | 85,236 | +18 |
| 9 Aug 2026, 09:51 | 85,218 | -2 |
| 8 Aug 2026, 07:27 | 85,220 | +14 |
| 7 Aug 2026, 04:11 | 85,206 | +31 |
| 6 Aug 2026, 02:30 | 85,175 | no change |
| 6 Aug 2026, 01:48 | 85,175 | first reading |
22 posts held, back to 23 July 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 17 pagesof 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 12 August 2026 |
|---|---|
| Posts held | 22 (23 July 2026 – 12 August 2026) |
| Views total | 1,086,410 |
| Reactions total | 52,499 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 18:46 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 12 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.
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.
50,421 reactions across 21 posts, in 3 distinct kinds. The most used accounts for 44.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5382265643103987288 | 22,468 | 44.6% | |
| custom 5382002945724296084 | 17,759 | 35.2% | |
| custom 5382174082991166262 | 10,194 | 20.2% |
Custom emoji. Every row above is a 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 22 of the 22 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 52,499reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 23 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.
https://vt.tiktok.com/ZS4K5s6yB/ сделал видосик, хочу посмотреть какими вы были тоже! жду ваши видосы
custom 5382265643103987288242custom 538217408299116626282custom 538200294572429608471
Москва, 23 августа!
custom 5382265643103987288374custom 5382002945724296084189custom 5382174082991166262131
0 дней общаюсь без негатива
custom 5382265643103987288919custom 5382174082991166262345custom 5382002945724296084314
3 день общаюсь без негатива
custom 5382002945724296084888custom 5382265643103987288372custom 5382174082991166262292
проходки этим красавчикам!
custom 53820029457242960841,280custom 5382174082991166262518custom 5382265643103987288452
Моему бате 53 года, он очень обожает творчество Арсения. Спасибо за заебический концерт. Дропаю видос с куском слэма
custom 53820029457242960842,310custom 53822656431039872881,070custom 5382174082991166262696
Нижний sank you so much!!!
custom 5382265643103987288857custom 5382002945724296084351custom 5382174082991166262251
Москва люблю!!!!
custom 53822656431039872881,230custom 5382174082991166262609custom 5382002945724296084457
вау, Питер спасибо!
custom 53820029457242960841,150custom 5382265643103987288602custom 5382174082991166262410
Теперь ждем твои лужники
custom 53820029457242960841,560custom 5382265643103987288770custom 5382174082991166262538
жесть, Лужники круто. 70к человек ничего не понял, все очень быстро, очень много людей, но волнения не было. Ваня легенда! теперь тоже хочу новых свершений всех люблю, я на дачу
custom 53822656431039872882,070custom 5382002945724296084812custom 5382174082991166262639
сегодня Ваня!
custom 53822656431039872881,210custom 5382002945724296084455custom 5382174082991166262310
Showing the 12 most recent of 22 posts we hold for @dogsl1fe. 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 — 1,421 of 1,084,084entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 71 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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.
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.
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Wikipedia
One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“SALUKI” (@dogsl1fe), 85,203 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dogsl1fe.
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.