Channel
@mellojapanes
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
50subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003243732383 |
|---|---|
| Type | Channel |
| Username | @mellojapanes |
| Created | Between 1 October 2025 and 29 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/mellojapanes |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 23:58 | 50 | no change |
| 13 Aug 2026, 17:17 | 50 | first reading |
11 posts held, back to 29 January 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 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 11 posts for this entry, the most recent from 3 May 2026. An engagement rate over an empty window would be a number about nothing.
452 reactions across 11 posts, in 56 distinct kinds. The most used accounts for 10.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5215208990295745575 | 46 | 10.2% | |
| custom 5379775631519156506 | 32 | 7.08% | |
| custom 5380043006118237174 | 32 | 7.08% | |
| custom 5343635341444143231 | 20 | 4.42% | |
| custom 5379627128729932510 | 20 | 4.42% | |
| custom 5217820953181972903 | 17 | 3.76% | |
| custom 5221971880159765753 | 17 | 3.76% | |
| custom 5339570438366321083 | 16 | 3.54% | |
| custom 5339344166604263650 | 15 | 3.32% | |
| custom 5145470863281226984 | 14 | 3.10% | |
| custom 5213467471251531532 | 12 | 2.65% | |
| custom 5222024450559469515 | 12 | 2.65% | |
| custom 5238084286761952085 | 12 | 2.65% | |
| custom 5211217840396329036 | 11 | 2.43% | |
| custom 5221970978216633721 | 10 | 2.21% | |
| custom 5384104821114563447 | 10 | 2.21% | |
| custom 5283066110613154342 | 9 | 1.99% | |
| custom 5210965188945142354 | 8 | 1.77% | |
| custom 5222232829487769685 | 8 | 1.77% | |
| custom 5226791121228690214 | 8 | 1.77% | |
| 36 further kinds | 123 | 27.2% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 11 of the 11 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 452reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 29 January 2026 to 3 May 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.
海が大きいのは、小さな川を軽視しないからです . . 🤩 𓈃͡ море потōму вēлико, что и мелкими речками не брезгŷет ⏔
custom 53664706732396756167custom 52628273356561816493custom 53663909973013692213custom 53686729864401796272custom 53687630476094091262custom 53686502617682135321custom 53687740470206527081custom 54339921375679242311
春三番 （harusanban） ㅤׅㅤꉹׄ 💇 . . южный ветер, который приносит опадание лепесткам сакуры ꢄ 🌸 ִ ㅤ
custom 52830661106131543427custom 52130692977184214604custom 52109651889451423543custom 52108850448553996292custom 52109337841442754282custom 52111448345422323261custom 52112082969789978741custom 53686502617682135321
人は失うことでしか、本当の価値が分からない。 𓏵 🥦 ࣪ человек понимāет ūстинную ценность лūшь чěрез утрату ꒰ 🌸 ︵︵
custom 533957043836632108316custom 521121784039632903611custom 52134674712515315329custom 52109651889451423545custom 52110864401668765192custom 52129321508227242292custom 52133018444276970342custom 53436353414441432312
古きを訪ねて新しきを知る изучая прошлое, мы познаем настоящее. ☔️
custom 533934416660426365015custom 53390912746349093396custom 53393841742246241696custom 54493686229987789185custom 53373048345277465063custom 53373236894341751492custom 53393878206518598062custom 54698883403565219242
𓂃 🪷 ° 老い木に花咲 и на сухом увядшẽм дереве рāстут цветы ᥀᥀ 🌟 . .
custom 522197097821663372110custom 538410482111456344710custom 52267911212286902148custom 53260610868882011833custom 52336027890362875972custom 52830661106131543422custom 53755494610092972632custom 53800430061182371742
ой
custom 52134674712515315323custom 52129321508227242292custom 53436353414441432312
朧月(обородзуки) - луна в дымке ̼ ᅠ 🖤⌢⌢ᅠᅠׅㅤ
custom 537977563151915650628custom 537962712872993251015custom 538004300611823717413custom 52152089902957455754custom 52605740068341235463custom 53436353414441432313custom 53798208618197510893custom 52178209531819729032
傷とは、光があなたに入ってくる場所である。 ┊ 🌟 ᨳᨳ рана — это место, через которое в тебя входит свет ꒰ 🎀 ꒱ ݂
custom 521520899029574557519custom 521782095318197290313custom 534363534144414323113custom 53800430061182371746custom 52605740068341235465custom 53796271287299325105custom 53797756315191565064custom 53798208618197510893
ㅤִ ♡ рамен магазин в Токио, прēдлагает стрǎнное мēню рамен с вǎнильным мороженым, а тáкже рамен с йогуртом, шоколадом, мõлоком ◌ 🌳 ៸៸
custom 521520899029574557513custom 51454708632812269846custom 54114707292270283425custom 52063042388959140484custom 53413394795609734274custom 53800430061182371744custom 54699547104861515203
в Японии на станции киси в гǒроде кинокāва префěктуры вакаяма нāзначили нøвого начальнūка вокзáла — кошку по кличке Ёнотама 🐈
custom 52222328294877696858custom 52152089902957455754custom 51454708632812269843custom 52198046224823358093custom 52247282956810579313custom 54699547104861515203custom 52178209531819729032custom 53800430061182371742
友情 в япōнии дружба - священное понятие, к нēй отнǒсятся щепетильно. ૮꒰◞ ◟ ꒱ა . 🤩 ︶ нāзвать другом в этой стране — практически породниться, это не прǒсто слово, ūм не рãзбрасывãются. éсли один раз проūзнесено «мы друзья», тǒ это понятûе стāраются пронести через всю жūзнь ꒰ 🤩 ɞɞ
custom 522197188015976575317custom 522202445055946951512custom 523808428676195208512custom 52152089902957455756custom 52222162337341378326custom 53280938433697773186custom 51454708632812269845custom 53800430061182371745
Showing the 11 most recent of 11 posts we hold for @mellojapanes. 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.
Citation-graph rank — 1,252,375 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“⏜ mꫀllꪮ j𐐼p𐐼nꫀs ꒰ ♡゙ ꒱” (@mellojapanes), 50 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/mellojapanes.
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.