Продам Гу Юмани 220 шт - 2$ Гу Яндекс 130 шт 5$ Гу Яндекс от 10 шт - 3$ Гу отработанные - 0.8$ Строки 160 шт - 1$ Мануал по Яндексу без форда - 20$

Channel
Seller GU
@SellerGUF
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
13subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003640874521 |
|---|---|
| Type | Channel |
| Username | @SellerGUF |
| Created | Between 1 December 2025 and 19 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 5 times, most recently 12 October 2026 |
| On Telegram | t.me/SellerGUF |
Topic
Hacking & security — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 23:18 | 13 | -1 |
| 16 Aug 2026, 15:46 | 14 | -1 |
| 11 Aug 2026, 23:45 | 15 | no change |
| 7 Aug 2026, 18:15 | 15 | first reading |
Engagement
19 posts held, back to 19 January 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 19 posts for this entry, the most recent from 21 February 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
В продаже мануалы по снятию 161/115 фз и укбо Цена 50$ Связь - @Pab05lo
В наличий большое количество ГУ под ВБ! По покупке писать @Pab05lo Готов обработать крупные заказы ЯП и ВБ по низкой цене!
🔥 Госы и строки в продаже! 🔥 Предлагаем вам актуальные базы для работы — идеально подойдут для верификаций и других задач! В наличии: ➖ Gos ⲅⲩ юⲙⲁⲏυ: 996 шт., цена — 3,0 $ ⲅⲩ яⲡⲉύ: 389 шт., цена — 6 $ ➖ Stroki Строки: 171 шт., цена — 1 $ Почему стоит выбрать нас? актуальные и проверенные базы; оперативный доступ после оплаты; поддержка по всем вопросам. Не упустите возможность пополнить свой арсенал качественными дан…
Готовые ГУ под ключ — выгодные цены, высокое качество 🔧 Всё, что нужно для быстрой установки — в одном комплекте. ГУ Юмани — 1081 шт. | $3 Надёжный выбор: проверенный спрос и доступная цена. ГУ ЯПэй — 512 шт. | $5 Премиум-сегмент: больше технологий, выше стоимость. Строки — 171 шт. | $1.5 Универсальное дополнение — идеально для комплектации. Оптимальное соотношение цены и наличия. Быстрая отгрузка, фиксированные …
На Госуслугах теперь можно смотреть долги других людей. В специальном сервисе будет виден номер и дата возбуждения исполнительного производства, основание для его открытия, сумма долга, название и адрес отдела судебных приставов, а также фамилия, имя и отчество пристава. Для проверки физлица нужно указать фамилию, имя и отчество, дату рождения и регион, где ведётся исполнительное производство. Для проверки юрлица — н…
🔥 В наличии ГУ с ИП и ООО По покупке @Pab05lo
🗄 Продам ГУ Б/У объем От 10 штук по 1$ от 100 штук по 0.5$ @Pab05lo
Подпишу сим - Йота 5.5 💵 Мегафон 5.5 💵 Т2 5.5💵 МТС 5.5 💵
🛍 ОГРОМНЫЙ объем Wb по низкой цене в наличий - @Pab05lo
Гу без номера | 7 шт | 4.0 $ Гу юмани/авито | 172 шт | 4.0 $ Гу со сканом | 7 шт | 12.0 $ Гу япэй | 101 шт | 6.5 $ Строки | 224 шт | 2 $
Залил Гу со сканом! Наличие 7 шт Цена 10$
Showing the 12 most recent of 19 posts we hold for @SellerGUF. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@SellerGUF named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 12 August 2026 – 12 August 2026
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“Seller GU” (@SellerGUF), 13 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/SellerGUF.
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.