Telegram RegisterThe public register of Telegram
Telegram profile photo for ⲡⲟⲕⲟύ ⲇⲩⲱυ

Channel

ⲡⲟⲕⲟύ ⲇⲩⲱυ

@pokkoydushi

On this record: Previous handles · Growth · Engagement · Posts · Cite this entry

7subscribers

+1 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-1001955181956
TypeChannel
Username@pokkoydushi
Created13 August 2023measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live29 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 29 August 2026
On Telegramt.me/pokkoydushi

Previous handles

@pokkoydushi was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@pokkoydushi
held 12 August 202612 August 2026

Growth

676.57 August 2026 — 6 subscribers12 August 2026 — 6 subscribers21 August 2026 — 7 subscribers7 August 202621 August 2026
3 measurements spanning 14 days, net +1. 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 6–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 22:087+1
12 Aug 2026, 21:466no change
7 Aug 2026, 12:276first reading

Engagement

8 posts held, back to 13 August 2023the 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 8 posts for this entry, the most recent from 21 December 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Dec 2025, 19:49 UTC12 viewsread 12 August 2026

величайшая потеря-это потеря Рая. что касается людей, они приходят и уходят.

21 Sept 2025, 20:23 UTC28 viewsread 12 August 2026

فليطفئ بحر دموع توبتك نار جهنم لك пусть море ваших слез покаяния, потушат вам огонь ада.

21 Sept 2025, 20:23 UTC28 viewsread 12 August 2026

يجب أن تكون قادرًا على التسامح والوداع أيضًا «Нужно уметь прощать, и прощатся тоже.»

12 Aug 2025, 20:03 UTC36 viewsread 12 August 2026

بغض النظر عن مدى هروبك من الأفكار خلال النهار، لا يزال الليل قادما. — сколько не убегай от мыслей днём, все равно наступает ночь.

4 Aug 2025, 09:02 UTC36 viewsread 12 August 2026

بعض الأحيان، العيش في الوحدة أنبل من العيش مع المنافقين. иногда жить в одиночестве достойнее, чем с фальшивыми

2 Aug 2025, 21:00 UTC29 viewsread 12 August 2026

-мы не были созданы для того, чтобы угодить созданиям

Showing the 8 most recent of 8 posts we hold for @pokkoydushi. 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.

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

“ⲡⲟⲕⲟύ ⲇⲩⲱυ” (@pokkoydushi), 7 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/pokkoydushi.

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.