Ребят подписывайтесь на новый чб арх по минхо и хенджину, там красивые постики 🐾🐾
Signed 𐔌 . ⋮𝒥𝑢𝑙𝑖.ᐟ ֹ ₊ ꒱🌸 ᶠˡᵒʷᵉ

Channel
@usdlykus
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,260subscribers
+382 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003868931226 |
|---|---|
| Type | Channel |
| Username | @usdlykus |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/usdlykus |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 21:59 | 1,260 | +54 |
| 12 Sept 2026, 07:38 | 1,206 | +22 |
| 8 Sept 2026, 13:16 | 1,184 | +31 |
| 3 Sept 2026, 15:37 | 1,153 | +33 |
| 31 Aug 2026, 18:07 | 1,120 | +40 |
| 28 Aug 2026, 11:24 | 1,080 | +44 |
| 25 Aug 2026, 04:58 | 1,036 | +130 |
| 19 Aug 2026, 03:35 | 906 | +31 |
| 11 Aug 2026, 20:42 | 875 | -3 |
| 10 Aug 2026, 21:46 | 878 | first reading |
18 posts held, back to 9 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
Ребят подписывайтесь на новый чб арх по минхо и хенджину, там красивые постики 🐾🐾
Signed 𐔌 . ⋮𝒥𝑢𝑙𝑖.ᐟ ֹ ₊ ꒱🌸 ᶠˡᵒʷᵉ
красивых кис и прекрасных юношей к нам в кф. приласкаем, пустим по кругу капризных малышей
Signed The Ivory Veil 1991’s ᶠˡᵒʷᵉ
даже не знаю с чего начать,вернулся в вирт недавно после ухода в год до этого тусовался на протяжении 3 лет.. хочу найти больше друзей,возможно даже кф,буду рад со всеми пообщаться можем завести огонек в тт,поиграть в колду,бс или же посидеть в рейве в общем,скучно не будет.главное найти общие темы )) @a959ye
Signed The Ivory Veil 1991’s ᶠˡᵒʷᵉ
Чп +4 мск, 18 в рж, уни, свободен. Ищу своего человека, с которым будет комфортно. Друг, сп - не важно, главное чтобы вы были хорошим человеком. Не хотел бы общаться с людьми младше 15 и старше 21, чп не важен, позиция тоже. @THUGGLIB
Signed 𐔌 . ⋮𝒥𝑢𝑙𝑖.ᐟ ֹ ₊ ꒱🌸 ᶠˡᵒʷᵉ
Нечем заняться в вирте? Лето проходит скучно? Тогда тебе к нам. . ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ KEEPERS — Это новый интерактивный канал,где ты можешь найти любимую игру, знакомства,а может и вторую половинку. Игры каждый день и каждый час. Также у нас открыт набор в стажёры . . Требования к стажёру Быть Старше 13 Лет Неконфликтность Выполнение Рассылок И Нормы ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ Если у вас нету опыт…
Signed 𐔌 . ⋮𝒥𝑢𝑙𝑖.ᐟ ֹ ₊ ꒱🌸 ᶠˡᵒʷᵉ
Красивых нью к нам в чат 16+ Дэлика ищет активных нью в чат с возрастным ограничением, небольшим количеством участников, чудесной администрацией и маленькой нормой. Давайте хорошо проведём время вместе🫂🫂 Свяжись с нами
Signed 𐔌 . ⋮𝒥𝑢𝑙𝑖.ᐟ ֹ ₊ ꒱🌸 ᶠˡᵒʷᵉ
охаешачки датебаешачки, давайте дружить пж @kteuoks
Signed The Ivory Veil 1991’s ᶠˡᵒʷᵉ
помогите мне к0нчить. @BabyKenhobot
Signed The Ivory Veil 1991’s ᶠˡᵒʷᵉ
ᅠ🩸. . SET IN ALVARADO'S CHAT 👍 ᅠᅠУсловия Для Вступления 📤Подписаться На Канал 📤Поставить Инициал 📤Кинуть Заявку В Чат Инициалы По Желанию. По Вопросам Писать @DarkangOfficial #repostalv
Signed The Ivory Veil 1991’s ᶠˡᵒʷᵉ
пусто @srqq_X
Signed The Ivory Veil 1991’s ᶠˡᵒʷᵉ
Нотвирт знакомств 15+
Signed 𐔌 . ⋮𝒥𝑢𝑙𝑖.ᐟ ֹ ₊ ꒱🌸 ᶠˡᵒʷᵉ
✧ возникают сомнения насчет верности партнера¿ ✧ хотите предложить отношения человеку, из-за которого бабочки в животе, но сомневаетесь в ответных чувствах¿ ✧ а может просто хотите расслабиться и приятно провести время в кругу других людей, поучаствовать в интерактивах и понаблюдать за интересными проверками¿ тогда за качественным времяпровождением вам точно …
Signed 𐔌 . ⋮𝒥𝑢𝑙𝑖.ᐟ ֹ ₊ ꒱🌸 ᶠˡᵒʷᵉ
Showing the 12 most recent of 18 posts we hold for @usdlykus. 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.
Named by 1 registered channel — 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.
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.
@usdlykus named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Ищу сп|друзей ᴸᵘᶜᵃˢ” (@usdlykus), 1,260 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/usdlykus.
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.