Channel
slay babe ♡☁️
@slayslay
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,070subscribers
-30 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001071851273 |
|---|---|
| Type | Channel |
| Username | @slayslay |
| Created | Between 1 October 2016 and 31 July 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/slayslay |
Topic
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 6 Nov 2026, 16:51 | 4,070 | -2 |
| 4 Nov 2026, 03:18 | 4,072 | -5 |
| 31 Oct 2026, 23:40 | 4,077 | +17 |
| 29 Oct 2026, 06:18 | 4,060 | +1 |
| 26 Oct 2026, 14:16 | 4,059 | -3 |
| 23 Oct 2026, 16:06 | 4,062 | +6 |
| 21 Oct 2026, 02:21 | 4,056 | +8 |
| 17 Oct 2026, 16:55 | 4,048 | -4 |
| 14 Oct 2026, 21:55 | 4,052 | -5 |
| 11 Oct 2026, 14:17 | 4,057 | -12 |
| 5 Oct 2026, 14:37 | 4,069 | -3 |
| 27 Sept 2026, 21:17 | 4,072 | -5 |
| 16 Sept 2026, 00:19 | 4,077 | +1 |
| 12 Sept 2026, 03:40 | 4,076 | -9 |
| 7 Sept 2026, 15:41 | 4,085 | -7 |
| 4 Sept 2026, 23:45 | 4,092 | no change |
| 2 Sept 2026, 19:35 | 4,092 | -6 |
| 30 Aug 2026, 13:05 | 4,098 | +2 |
| 27 Aug 2026, 10:35 | 4,096 | +3 |
| 24 Aug 2026, 09:13 | 4,093 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.
@Soundbaar · 40,729
Telegram ranks this channel #38 of 78 here — alongside 77 others — read 30 August 2026
@honeyprrofficial · 43,032
Telegram ranks this channel #68 of 80 here — alongside 79 others — read 27 August 2026
@amiralichannel · 68,112
Telegram ranks this channel #84 of 93 here — alongside 92 others — read 20 August 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“slay babe ♡☁️” (@slayslay), 4,070 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/slayslay.
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.