17 Sept 2026, 16:38 UTC1 viewsread 18 September 2026
Forwarded from @MonocorpsPhoto
@naigumo ft. @eWeak @homsal @nrerd
Channel
Archive.
@EucharistHoly
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 13 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003877996276 |
|---|---|
| Type | Channel |
| Username | @EucharistHoly |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 29 October 2026 |
| Measurements held | 2 |
| On Telegram | t.me/EucharistHoly |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 05:23 | 1 | no change |
| 13 Sept 2026, 11:17 | 1 | first reading |
Engagement
15 posts held, back to 14 September 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 15 posts for this entry, the most recent from 17 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 31
- Videos
- 4
- Links
- 16
Lifetime counters from Telegram’s own channel header, read 18 September 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.
- Video runtime
- 27s
- Average length
- 14s
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
17 Sept 2026, 10:39 UTC1 viewsread 18 September 2026
Photo
@inyoue & @usuallyy, @naigumo, @pitchhy, @bunniho, @rYihan.
15 Sept 2026, 12:53 UTC1 viewsread 18 September 2026
Forwarded from @auraIis
@naigumo. ♥️ i’ve seen him literally like everywhere before we even know each other. my other mutuals mentioned him many times, but he also commented everywhere tho. hal pertama yang aku notice ketika lihat tensen adalah @ pu nya. karna apa? karna aku pacar nagumo. jujur kalo udah bahas nagumo rasanya besar banget gejolak cinta di hatiku karna aku memang cinta nagumo. tapi itu ga penting, yang penting adalah hal yan…
15 Sept 2026, 12:28 UTC1 viewsread 18 September 2026
Photo
@miaachi ft. @Olderr @wBury @Centilp @Junkoo @naigumo @aumane @Juhoong @usuallyy @rGempal @prominaq
15 Sept 2026, 11:07 UTC1 viewsread 18 September 2026
Forwarded from @iglooiPhoto
@eweak ft. @obsessz @ppermata @jeongiak @kajeIIe @toughn @sqanrio @naigumo @usuallyy @pitchyy @hwolf @eiexn
14 Sept 2026, 14:11 UTC5 viewsread 18 September 2026
Forwarded from @Monocorps
Otsukare SUMMER by HALCALI reminds me of @pitchhy!
14 Sept 2026, 14:11 UTC4 viewsread 18 September 2026
Forwarded from @Monocorps
Chest Pain (I Love) by Malcolm Todd reminds me of @Olderr.
14 Sept 2026, 14:11 UTC4 viewsread 18 September 2026
Forwarded from @Monocorps
Infrunami by Steve Lacy reminds me of @miaachi.
14 Sept 2026, 14:11 UTC4 viewsread 18 September 2026
Forwarded from @Monocorps
See You by Johnny Orlando reminds me of @eWeak.
14 Sept 2026, 14:11 UTC5 viewsread 18 September 2026
Forwarded from @Monocorps
Beautiful People by Ed Sheeran reminds of @lleire.
14 Sept 2026, 14:11 UTC7 viewsread 18 September 2026
Forwarded from @Monocorps
TICTAC by CAPSULE reminds me of @elogwyn!
14 Sept 2026, 14:11 UTC7 viewsread 18 September 2026
Forwarded from @Monocorps
Like a Stone by Audioslave reminds me of @ddnfi.
Showing the 12 most recent of 15 posts we hold for @EucharistHoly. 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
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Archive.” (@EucharistHoly), 1 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/EucharistHoly.
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.