мы не мы?

Channel
саша теслонд @teslond
@teslond1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
88,183subscribers
-14,631 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001523317568 |
|---|---|
| Type | Channel |
| Username | @teslond1 |
| Description | сотрудничество: [email protected] мой секонд-хенд -> https://t.me/secondbyteslond По вопросам разбана в чате писать @Vasya_Kashin A+ : https://www.gosuslugi.ru/snet/673de079340096358bbcdac5 |
| Created | 25 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/teslond1 |
Topic
Music — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 05:10 | 88,183 | -456 |
| 11 Nov 2026, 09:38 | 88,639 | -297 |
| 9 Nov 2026, 17:20 | 88,936 | -277 |
| 8 Nov 2026, 09:39 | 89,213 | -140 |
| 7 Nov 2026, 03:37 | 89,353 | -119 |
| 6 Nov 2026, 00:56 | 89,472 | -177 |
| 5 Nov 2026, 01:31 | 89,649 | -151 |
| 3 Nov 2026, 22:29 | 89,800 | -159 |
| 2 Nov 2026, 20:59 | 89,959 | -87 |
| 1 Nov 2026, 23:10 | 90,046 | -138 |
| 1 Nov 2026, 01:38 | 90,184 | -121 |
| 31 Oct 2026, 05:07 | 90,305 | -124 |
| 30 Oct 2026, 06:37 | 90,429 | -195 |
| 29 Oct 2026, 05:58 | 90,624 | -152 |
| 28 Oct 2026, 01:30 | 90,776 | -127 |
| 27 Oct 2026, 03:15 | 90,903 | -181 |
| 26 Oct 2026, 03:06 | 91,084 | -62 |
| 25 Oct 2026, 03:05 | 91,146 | -95 |
| 23 Oct 2026, 23:36 | 91,241 | -124 |
| 23 Oct 2026, 01:58 | 91,365 | first reading |
Engagement
241 posts held, back to 5 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 211 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 13.7%
- avg views ÷ 88,183 subscribers
- Avg views / post
- 12,100
- 84 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 86
- of 241 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.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 241 (5 August 2026 – 16 November 2026) |
| Views total | 1,014,960 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 09:51 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
- ≈12,100
- Videos
- ≈1,650
- Links
- ≈980
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 28m 10s
- Average length
- 23s
Measured directly from 73 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
26,035 reactions across 79 posts, in 2 distinct kinds. The most used accounts for 64.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5415914542909645708 | 16,839 | 64.7% | |
| ❤ | 9,196 | 35.3% |
Custom emoji. One 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 count beside it is Telegram’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 80 of the 241 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 26,258 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 241 most recent posts we hold, published 5 August 2026 to 16 November 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
- 89
- across the posts below
- Posts paid on
- 23
- of 231 we hold a reading for · 10%
- Most on one post
- 46
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @teslond1. 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 241 most recent posts we hold for this entry, published 5 August 2026 to 16 November 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
Telegram’s own ‘edited’ marker: 4 of 86 posts held from the last 30 days (4.65%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
вот так проходят мои диджей гастроли 🇪🇺🪩🕺🏼 20.11 Мюнхен 🇩🇪 27.11 Грац 🇦🇹 28.11 Париж 🇫🇷 везде сделали опцию мит’н’грита, чтобы мы могли пообщаться пофоткаться в спокойной обстановке 🫂🥰 БИЛЕТЫ🎟️🎟️🎟️ все аутфиты из этого ролика из @ultima_market
и где он не прав?
📍Genève, Switzerland 🇨🇭
I LOVE HER SO MUCH
какой прекрасный вечер чтобы… зайти в мою сешкуууу (можно торговаться) https://t.me/secondbyteslond
Video message, posted without a caption
Максимальный репост
также эта же рок-звезда в 9 утра вылетает в женеву потому что вечером сееееет уже там 🇨🇭🧀 тикетсы можно взять по ссылке, обещаю ставить вилиана и мэдкида посоветуйте куда сходить в женеве??
я раздаю в 3:00 в клубе в гамбурге
я угараю как мой тг превратился в доску объявлений…есть ли кто тут из вас мои французы кто есть в приложении gensdeconfiance если да, то могли бы вы мне пожалуйста написать @teslond21 поможем мне найти квартиру вашими молитвами….
думали я вас оставлю без открыток?!??!? нет.
Showing the 12 most recent of 241 posts we hold for @teslond1. 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.
Posts recorded as deleted after publishing
We recorded 4 posts on @teslond1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 15 September 2026
- Most recent seen missing
- 19 October 2026
- Median time before seen missing
- 20 hours
- Seen missing in the last 30 days
- 1
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@arinanedura · 18,7131 postБЭД БАРБИ💅🏻
@badbarbieeee · 44,7231 postБулавка в мире моды
@fashionsegment · 24,8731 postЛучшая подружка | Ksenia Hoffman
@hoffmanteam · 82,1111 postснежана вещает
@navysokix · 1691 postПАНКУША
@pnksha · 22,0631 postWorldwide Consulting
@wceverywhere · 11,6561 post
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.
Mentions
Named by 6 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.
@teslond · 88 postssecond by teslond
@secondbyteslond · 3,6515 postsПодруги секонд
@girlysecondstore · 1,8602 postsStudio Slow
@studioslow · 20,3042 postsРедакция Ultima Яндекс Маркета
@Ultima_Market · 47,4782 posts✨ADUSHCLUB✨ Катя Адушкина
@Adushkinaa · 85,2861 postБ Э К
@beck_event · 2,8171 postДОКТОР ПЕРСАТИ | ЛЕЧЕНИЕ АКНЕ
@drpersati · 4,9701 postне тереби дао
@dukaliti · 121,5151 postКРУТО
@krutofestival · 5,5361 postПокупка билетов Qtickets
@QticketsBuyBot · 47,2431 postUNeedCam
@uneedcam · 14,9201 postWorldwide Consulting
@wceverywhere · 11,6561 post
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.
Appears in Telegram’s recommendations for other channels
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.
@barrashikliza · 351,772
Telegram ranks this channel #3 of 53 here — alongside 52 others — read 24 August 2026
@dimavodima · 41,547
Telegram ranks this channel #7 of 42 here — alongside 41 others — read 29 August 2026
@sashaspilberg · 40,387
Telegram ranks this channel #13 of 65 here — alongside 64 others — read 29 August 2026
@nelljoule · 19,479
Telegram ranks this channel #20 of 58 here — alongside 57 others — read 28 September 2026
@badbarbieeee · 44,723
Telegram ranks this channel #26 of 51 here — alongside 50 others — read 27 August 2026
@miamonamii · 22,301
Telegram ranks this channel #28 of 34 here — alongside 33 others — read 20 September 2026
@dankakriv · 54,267
Telegram ranks this channel #32 of 57 here — alongside 56 others — read 24 August 2026
@dariniiii · 19,378
Telegram ranks this channel #33 of 38 here — alongside 37 others — read 1 October 2026
@youngroyals_netflix_tg · 57,642
Telegram ranks this channel #35 of 56 here — alongside 55 others — read 27 August 2026
@fukiingdom · 38,433
Telegram ranks this channel #38 of 57 here — alongside 56 others — read 28 September 2026
@frontroww · 46,625
Telegram ranks this channel #38 of 69 here — alongside 68 others — read 27 August 2026
@krisbeautynews · 53,734
Telegram ranks this channel #38 of 63 here — alongside 62 others — read 24 August 2026
@ZKjlILKh8JM3MDQ6 · 19,625
Telegram ranks this channel #39 of 39 here — alongside 38 others — read 1 October 2026
@sosomakinst · 22,766
Telegram ranks this channel #39 of 47 here — alongside 46 others — read 20 September 2026
@lenabalykina · 43,417
Telegram ranks this channel #42 of 56 here — alongside 55 others — read 28 August 2026
@savchikhina · 47,848
Telegram ranks this channel #44 of 60 here — alongside 59 others — read 28 September 2026
@lavrisonn · 21,065
Telegram ranks this channel #44 of 48 here — alongside 47 others — read 22 September 2026
@salavat_kypere · 46,287
Telegram ranks this channel #44 of 64 here — alongside 63 others — read 27 August 2026
@lookonline1 · 47,636
Telegram ranks this channel #44 of 60 here — alongside 59 others — read 27 August 2026
@arlovedbyyouuu · 74,285
Telegram ranks this channel #44 of 48 here — alongside 47 others — read 24 August 2026
@exeqwertalena · 63,668
Telegram ranks this channel #45 of 48 here — alongside 47 others — read 24 August 2026
@lovatikann · 47,618
Telegram ranks this channel #49 of 65 here — alongside 64 others — read 25 August 2026
@myhotelki · 48,050
Telegram ranks this channel #51 of 86 here — alongside 85 others — read 26 August 2026
@rutkismary · 337,386
Telegram ranks this channel #52 of 57 here — alongside 56 others — read 10 August 2026
This channel appears in 75 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“саша теслонд @teslond” (@teslond1), 88,183 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/teslond1.
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.