Telegram RegisterThe public register of Telegram

Channel

— 𝒜eleαѕнα⋆⋆

@foorryyou

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

200subscribers

+0 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-1001410651225
TypeChannel
Username@foorryyou
Description❝ digenggam, di angankan, lalu di hempaskan ❞ contact ↬ @urrdiraaa_bot (anything) pfp ↬ @pfpdira_bot connect↬ @urrdiiraa @gjegbut store ↬ @tokosnowpuff (n) bisain kalo mau ambil di cr ya Cr. Admin dan sosmed Since 23 april 2021
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/foorryyou

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 68% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@gjegbut/1285518 Feb 2023, 00:38 UTC@foorryyou/15068 · this entry18 Feb 2023, 00:38 UTC1.00under a minute
@gjegbut/1285618 Feb 2023, 00:59 UTC@foorryyou/15069 · this entry18 Feb 2023, 00:59 UTC1.00under a minute
@foorryyou/15070 · this entry18 Feb 2023, 08:02 UTC@gjegbut/1285718 Feb 2023, 08:03 UTC1.0072 seconds
@foorryyou/15071 · this entry19 Feb 2023, 02:15 UTC@gjegbut/1285819 Feb 2023, 02:16 UTC1.00under a minute
@foorryyou/15072 · this entry19 Feb 2023, 02:23 UTC@gjegbut/1285919 Feb 2023, 02:24 UTC1.0072 seconds
@foorryyou/15073 · this entry22 Feb 2023, 15:16 UTC@gjegbut/1286022 Feb 2023, 15:26 UTC1.0010 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@gjegbut9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (72)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 2 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 9 comparable posts for this entry, running 18 February 2023 to 24 August 2024. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @gjegbut. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2007 Aug 2026, 02:04 — 200 subscribers7 Aug 2026, 04:02 — 200 subscribers7 Aug 2026, 02:047 Aug 2026, 04:02
2 measurements taken within a single day. 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 199–201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 04:02200no change
7 Aug 2026, 02:04200first reading

Engagement

20 posts held, back to 4 January 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 pageof 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 24 August 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
175
Videos
5
Links
41

Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

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 3 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 1reactions 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 4 January 2023 to 24 August 2024, 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

24 Aug 2024, 01:32 UTC137 viewsread 7 August 2026

andai kau tahu betapa hancurnya aku, ketika aku memutuskan untuk menjauh darimu, padahal sebenarnya aku masih ingin selalu bersamamu.

Signed anin

24 Jul 2024, 15:01 UTC162 viewsread 7 August 2026

bagian mana yang tak kumaklumi? bahkan sakitpun ku terima dengan senang hati haha

Signed anin

21 Jul 2024, 04:38 UTC171 viewsread 7 August 2026

ternyata diam dan ga berisik dalam hal apapun itu menenangkan walau minusnya kesepian tapi gpp

Signed anin

14 Jul 2024, 14:42 UTC188 viewsread 7 August 2026

pd akhirny ttp aku penjahatnya diceritamu, pdhal dsni aku mati2an bertahan n mmprjuangkan bhkn skrng skdr untuk tenang pun aku tk bisa. baik baik kamu.

Signed anin #𝐂rown𝐀uriga

13 Jul 2024, 07:03 UTC177 viewsread 7 August 2026

melepaskan karna keterpaksaan itu sakit ya, bahkan untuk melupakan nya saja sangat sulit

Signed anin #𝐂rown𝐀uriga

3 May 2023, 13:04 UTC564 views0 reactionsread 7 August 2026

bahkan yang sudah berjanji pun, masih bisa meninggalkan

Signed anin

2 May 2023, 23:32 UTC553 viewsread 7 August 2026

terlalu menutup hati hingga lupa cara untuk membukanya kembali

Signed anin

22 Feb 2023, 15:21 UTC701 viewsread 7 August 2026

aku ingin kau bahagia, walau tidak denganku, walau harus aku yang terluka. jujur, berpisah denganmu adalah takdir Tuhan yang paling tidak aku inginkan. namun, disisi lain aku percaya, kehendaknya adalah jalan yang pasti akan berujung Indah, pilihannya adalah tepat yang pasti akan sama-sama kita syukuri suatu saat. walau harus kenyataan pahit dulu yang diterima, harus luka dalam dulu yang didapatkan, dan harus air m

Signed anin

22 Feb 2023, 15:16 UTC447 viewsread 7 August 2026

walau harus aku yang terluka. "bila akhirnya takdir tidak mempersatukanku denganmu, aku tidak akan pernah menyesal mencintaimu sedalam itu. namun ketahuilah, ada banyak air mata yang jatuh saat aku menulis kalimat ini."

Signed anin

19 Feb 2023, 02:23 UTC503 views1 reactionsread 7 August 2026

tidak, tidak ada lagi yang dapat aku perjuangkan, aku rasa telah tiba saatnya untukku membiarkanmu berlalu, membiarkanmu memilih yang terbaik bagimu. bertahan dengan hati yang tidak ingin dipertahankan, kau pun tahu, tidak ada siapapun yang sanggup. maaf untuk segalanya. entah siapa setelah aku nanti, entah siapa yang kau pilih sebagai pengganti, Aku harap dia adalah seseorang yang tulus menyayangimu, yang pandai m

👍1

Signed anin

Showing the 12 most recent of 20 posts we hold for @foorryyou. 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 7 August 2026 — this entry's latest reading, not the date you are reading this.

“— 𝒜eleαѕнα⋆⋆” (@foorryyou), 200 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/foorryyou.

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.