Telegram RegisterThe public register of Telegram
Telegram profile photo for 🍗🥓🧅

Channel

🍗🥓🧅

@fuckyzewe

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

73subscribers

-4 since we began measuring on 29 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003304218067
TypeChannel
Username@fuckyzewe
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 August 2026
Last confirmed live21 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 21 October 2026
On Telegramt.me/fuckyzewe

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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

737875.529 August 2026 — 77 subscribers29 August 2026 — 77 subscribers7 September 2026 — 78 subscribers29 September 2026 — 77 subscribers8 October 2026 — 78 subscribers15 October 2026 — 74 subscribers21 October 2026 — 73 subscribers29 August 202621 October 2026
7 measurements spanning 53 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 72–79 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Oct 2026, 21:1173-1
15 Oct 2026, 01:3174-4
8 Oct 2026, 19:3678+1
29 Sept 2026, 04:3977-1
7 Sept 2026, 10:5878+1
29 Aug 2026, 14:4577no change
29 Aug 2026, 14:3077first reading

Engagement

18 posts held, back to 17 May 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 26 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Jul 2026, 15:22 UTC252 viewsread 29 August 2026

vless://[email protected]:443?security=tls&allowInsecure=1&type=tcp#vless БОТ СТОИТ НА ЛУЧШЕМ ХОСТИНГЕ ДЛЯ БОТОВ CTRLFREE (все кнопочки работают)

22 Jul 2026, 23:18 UTC255 viewsread 29 August 2026
File

БОТ СТОИТ НА ЛУЧШЕМ ХОСТИНГЕ ДЛЯ БОТОВ CTRLFREE (все кнопочки работают)

22 Jul 2026, 23:17 UTC240 viewsread 29 August 2026

Опять поднял бота, добавил инлайн

26 Jun 2026, 04:00 UTC428 viewsread 29 August 2026

В связи с тем, что на GitHub участились случаи, когда конфигурация сервиса обнаруживается сканерами и становится недоступной, репозиторий на GitHub закрыт на неопределённое время. Новые ссылки: yahuy.eu.cc yahuy.eu.cc/purple.txt Для Clash клиентов: yahuy.eu.cc/yaml yahuy.eu.cc/purple.yaml БС зеркало остаётся в прежнем формате: https://clck.ru/3Tju7N Clash: https://clck.ru/3UDjZJ Также напоминаю, что эти конфи…

19 Jun 2026, 23:42 UTC417 viewsread 29 August 2026
File

tg://proxy?server=51.250.82.16&port=443&secret=eeb72954885d6fd069f16372f54e9c9939656467652e6c6962726176612e636c69636b tg://proxy?server=185.241.193.187&port=443&secret=eedcaae509a2455bbfc6165f1708fd5c586d61782e7275 Plugin TGWS Outside Mihomo

19 Jun 2026, 23:42 UTC375 viewsread 29 August 2026

Только бсные прокси, потому что чсных слишком много: tg://proxy?server=185.241.193.179&port=443&secret=eedcaae509a2455bbfc6165f1708fd5c586d61782e7275 tg://proxy?server=37.139.35.12&port=443&secret=ee2ed7517b077ef414e24b106e0729335d6d742e636f7270682e7275 tg://proxy?server=51.250.79.96&port=443&secret=eec9c9bb1b8b220bfb0517e575dc34e1e563646e2e736176656c7965762e636c69636b tg://proxy?server=62.84.112.46&port=443&secre…

19 Jun 2026, 23:25 UTC293 viewsread 29 August 2026
Forwarded from @prsdrty_KLIRNETPhoto

Photo, posted without a caption

17 Jun 2026, 12:50 UTC290 viewsread 29 August 2026

Добавил конфигурации для Clash клиентов Git БС

9 Jun 2026, 05:48 UTC356 viewsread 29 August 2026
File

Бс: tg://proxy?server=51.250.92.104&port=443&secret=ee6a0333c1db3f8eaba5c76731a44203b6617669746f2e7275 tg://proxy?server=130.193.37.35&port=443&secret=eef759f32d70c17cef76b34ab18561ff7972617069642e717569636b726f7574656170702e78797a tg://proxy?server=51.250.31.46&port=443&secret=ee2d3817c6b2bf469fb5064e6cb4b19790617669746f2e7275 tg://proxy?server=87.229.56.15&port=443&secret=ee1603010200010001fc030386e24c3add62697…

9 Jun 2026, 05:47 UTC326 viewsread 29 August 2026
File

tg://proxy?server=93.77.165.253&port=443&secret=eedb7eda819ee3499ac5f5d2a8803be174747572626f2e70726f787974656c6567612e73746f7265 tg://proxy?server=93.77.162.5&port=443&secret=eeb4cf448c2c66dc6151b6746bd1799ae5676c6964652e70726f78796f6e6c696e652e6f6e6c696e65 tg://proxy?server=93.77.162.105&port=443&secret=eee12b7ef9718c53b06c8a416387c8d4a6776176652e70726f787974656c6567612e73746f7265 tg://proxy?server=93.77.167.20&p…

Showing the 12 most recent of 18 posts we hold for @fuckyzewe. 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.

Forward network

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 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.

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 21 October 2026 — this entry's latest reading, not the date you are reading this.

“🍗🥓🧅” (@fuckyzewe), 73 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/fuckyzewe.

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.