Telegram RegisterThe public register of Telegram
Telegram profile photo for [004] ƨivɘɿd ɒɟiv ,ɒϱnol ƨɿA

Channel

[004] ƨivɘɿd ɒɟiv ,ɒϱnol ƨɿA

@triantafyllon

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

19subscribers

+1 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1004473856165
TypeChannel
Username@triantafyllon
CreatedBetween 1 June 2026 and 9 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live1 September 2026
Measurements held3
Confirmed unchanged3 times, most recently 1 September 2026
On Telegramt.me/triantafyllon

Growth

181918.59 August 2026 — 18 subscribers11 August 2026 — 18 subscribers17 August 2026 — 19 subscribers9 August 202617 August 2026
3 measurements spanning 8 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 18–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 19:3819+1
11 Aug 2026, 19:1618no change
9 Aug 2026, 11:0018first reading

Engagement

20 posts held, back to 9 July 2026the 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 20 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

15 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🕊1066.7%
👀533.3%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 6 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 15 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 9 July 2026 to 2 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

2 Aug 2026, 10:29 UTC12 viewsread 11 August 2026

ɐɓʎɯɯо ǝоннǝǹ ǝоwɐɔ ʁнǝw ʎ vɐdƍоɯо оɯ-оɯʞ ıqƍоɯҺ ,ɐvǝɯох ǝн ıqƍ ʁ ¿ıqƍqɔоdu иоw ɯǝʁdǝʚоdu оɯʞ ,wǝɯ qɯʁdǝʚоɓ иv ɯиоɯɔ [❓❓]

31 Jul 2026, 15:09 UTC15 viewsread 11 August 2026

oıdɐɓоɹɐvƍ ˙ɯɔʎ хиоʚɯ εи иɯɔǝʚ ņонqvǝɯɐҺǝwɐε ʁvɓ ʎɓɐdɹǝdu ɐvɐɓ ǝн ɐvɔиҺ ɐʚɓ ɐн ɐǹинεɐd ɐmɐн ǝжɐɓ [🐰🌸🕸]

31 Jul 2026, 14:37 UTC15 viewsread 11 August 2026

хǝɔʚ ʁvɓ ɯнǝwоw ņıqнжɐʚ онqvоʚоɓ оɯє ,ɯǝн онҺǝноʞ ¿qɯиuʎɯɔоu ņоƍоɯ ɔ ʎɹоw ʞɐɯ ʁ ʞɐʞ [👀]

31 Jul 2026, 14:00 UTC15 viewsread 11 August 2026

ǝинɐvǝж оʞqvоɯ ɔɐʚ ɔ ¿ǝинǝvʚʁqƍо ǝоʞǝн иɯɔǝнεиоdu ʎwоннǝʚɯɔǝжdоɯ оu ıqƍ ɹоw оɯʞ ,ǝıqннǝҺoıvʞɐε ǝиɹоdоɓ [👁]

20 Jul 2026, 10:09 UTC33 viewsread 11 August 2026

¿ʁнǝw qɯиvεоu ıqƍоɯҺ ,оɹоɯ ʁvɓ оɯɔоdu оɯє иvи онmǝwɔ оɹоɯє ɔ онqvɐǝd wɐʚ [🤩]

20 Jul 2026, 10:07 UTC33 viewsread 11 August 2026
Photo

⭐ фотография ¿ɐvɐҺɐн ıqɯон ņоɯ ɔ ǝн ʁ qɯıqƍ ɯǝжоw ˙ņоннǝvɐҺǝuо ˙˙˙оɹонwǝн ʁнǝw ɯǝɐvǝɓ ǝɯǝʁvоʚεоu ǝƍǝɔ ıqʚ оɯҺ ,оɯ ʁɓиʚ ɐ ,ʁнǝw оɓ иʞинεoıоɔ — ıqʚ оɯҺ ,ɐvɐɓижо ʁ ˙dоwoı ņиʞɔоvu онqvɐwиɔʞɐw оɯє оɯҺ ,оɹоɯ ɔ wǝнҺɐн ǝɯņɐʚɐɓ [🎶]

10 Jul 2026, 12:30 UTC51 views2 reactionsread 11 August 2026

[🪽] если что! меня кинули в землюヾ⁠(⁠*⁠’⁠O⁠’⁠*⁠)⁠/

🕊2

10 Jul 2026, 12:28 UTC49 views3 reactionsread 11 August 2026

[ИСКУССТВО] 🪦🕯️ ⚰️ 🍋🪽

🕊2👀1

10 Jul 2026, 12:23 UTC44 viewsread 11 August 2026

[🪽] прости меня!!! я не умею читать(⁠。⁠・⁠ω⁠・⁠。⁠)⁠ノ⁠♡ я не знаком с твоим делом и уж с тобой тем более (⁠゜⁠o⁠゜⁠; я извиняюсь и изучу документы получше! ヾ⁠(⁠*⁠’⁠O⁠’⁠*⁠)⁠/

10 Jul 2026, 12:18 UTC36 viewsread 11 August 2026

[🪽] о великая госпожа Ия. я имел в виду, что ваш театр замечательный! просто моя одна извилина, пока что, не может обработать это(⁠ꏿ⁠﹏⁠ꏿ⁠;⁠) аминь аминь аминь госпоже (⁠♡⁠ω⁠♡⁠ ⁠)⁠ ⁠~⁠♪

10 Jul 2026, 12:06 UTC35 viewsread 11 August 2026

инεиж ʚ иʞɯıquоu иоʚɯ ɐн ıqǹинεɐd εǝƍ ǝн ʎwоʞ ижɐʞоu [🪽] [🪽] я идиот◉⁠‿⁠◉ я идиот(⁠.⁠ ⁠❛⁠ ⁠ᴗ⁠ ⁠❛⁠.⁠) у меня нет мозгов ╮⁠(⁠.⁠ ⁠❛⁠ ⁠ᴗ⁠ ⁠❛⁠.⁠)⁠╭ мне трудно существовать как единица в этом социуме(⁠╬⁠☉⁠д⁠⊙⁠)⁠⊰⁠⊹ฺ

10 Jul 2026, 12:02 UTC28 views1 reactionsread 11 August 2026

жохоu хин ɐн wоɯє ʚ ıqɯ [🪽]

🕊1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 registered channels — 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.

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

“[004] ƨivɘɿd ɒɟiv ,ɒϱnol ƨɿA” (@triantafyllon), 19 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/triantafyllon.

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.