Telegram RegisterThe public register of Telegram
Telegram profile photo for ๑︎ 忄ŋẝܘ ღ𝐚𝘳▏ܘധ 𖧁୧

Channel

๑︎ 忄ŋẝܘ ღ𝐚𝘳▏ܘധ 𖧁୧

@marlowwwloverspokishere

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

39subscribers

-13 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002861627882
TypeChannel
Username@marlowwwloverspokishere
Created7 August 2025 — measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live18 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/marlowwwloverspokishere

Growth

395245.515 August 2026 — 52 subscribers16 August 2026 — 51 subscribers24 August 2026 — 49 subscribers31 August 2026 — 47 subscribers10 September 2026 — 43 subscribers18 September 2026 — 39 subscribers15 August 202618 September 2026
6 measurements spanning 34 days, net -13. 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 37–54 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 08:3939-4
10 Sept 2026, 11:5743-4
31 Aug 2026, 12:1447-2
24 Aug 2026, 13:0249-2
16 Aug 2026, 18:1451-1
15 Aug 2026, 12:3152first reading

Engagement

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

Reaction mix

1,539 reactions across 10 posts, in 23 distinct kinds. The most used accounts for 14.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 539786144674484167923014.9%
❤‍🔥21514.0%
💘21514.0%
🍓1288.32%
custom 54003761887513514241117.21%
👍996.43%
💋885.72%
custom 5402091912221987246694.48%
custom 5397929315818049010674.35%
custom 5400249826518536223583.77%
custom 5395874680773057605523.38%
custom 5399820828005145100523.38%
💔312.01%
custom 5397798748812252033271.75%
💊221.43%
👌150.975%
😍140.91%
custom 5399925861430365321110.715%
custom 5395370524626948800100.65%
custom 539325938069724693480.52%
3 further kinds171.10%

Custom emoji. 11 of the rows above are 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 are Telegram’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 10 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 1,539 reactions 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 7 August 2025 to 15 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

15 Aug 2026, 11:50 UTC22 views23 reactionsread 15 August 2026
Forwarded from @tupaiusPhoto

⸝⸝ ТУПА Я — СПОУК ( #unstableuniverse )

custom 53932593806972469348custom 53956692224225185427custom 53978614467448416796custom 53956394668890950142

14 Feb 2026, 14:09 UTC711 views123 reactionsread 15 August 2026
Photo

Photo, posted without a caption

custom 540209191222198724642custom 540037618875135142423custom 539587468077305760518custom 539982082800514510010custom 53977987488122520338custom 54002498265185362238custom 53978614467448416797custom 53979293158180490107

6 Feb 2026, 12:26 UTC815 views99 reactionsread 15 August 2026
Forwarded from @tupaiusPhoto

⸝⸝ он — 10/10, но... это тупа споук ( #lifesteal )

custom 539786144674484167927🍓18custom 540037618875135142416custom 540024982651853622314custom 539982082800514510012custom 540209191222198724612

3 Feb 2026, 13:35 UTC974 views124 reactionsread 15 August 2026
Photo

🎀🤩 Ƚ⚬៴୧ เ𝔧Ꭶቲיִ ₍ ╥ħ୧ ⚬𝘳ᵭ୧𝘳 ᵭ⚬୧Ꭶԉˈቲ ෆ𝐚ቲቲ୧𝘳⁾ 🤩🤩 🎀 🐏𝓙⚬ħᥰᥰұ ⋞𝟑 , ₳𝘳␢ұ𝘇 , ღ𝔧Ꭶ𝐚, ღұ𝝌𝐚, Ɖ୧𝔧 , ₭𝔧Ꝅ𝔧ෆ⚬𝘳𝐚 , Ꮥ⚬ෆᥰ𝔧 , 𝓕𝐚⨎𝔧ᥰ , 𝐑⚬𝓦𝐚ᥰ , 𝜨𝛔Ɏ𝓿𝐚ƞ, ℋ𝐚ᣴꝄ൦Ꭶħ𝐚 🐏 🐏 ╽ เ⚬៴୧ ෆұ ⨎𝘳𝔧୧ᥰᵭᎦ ៴୧𝘳ұ ෆυcħיִ 🐏

custom 539786144674484167936custom 540037618875135142436custom 539792931581804901022🍓13custom 53958746807730576059custom 53998208280051451008

1 Feb 2026, 17:09 UTC921 views169 reactionsread 15 August 2026
Forwarded from @tupaiusPhoto

⸝⸝ ТУПА Я — СПОУК ( #plush #lifestealsmp )

custom 539786144674484167955💘32💋23custom 539792931581804901010custom 54002498265185362238🍓7😍7custom 53958746807730576057

31 Jan 2026, 18:43 UTC945 views164 reactionsread 15 August 2026
Photo

🎀🐏".₩ħ𝐚† ίᎦ Ɏ𝛔𝐮𝘳 𝛔Ꭾίƞί𝛔ƞ 𝐚␢𝛔𝐮† ෆ୧? ". 🐏 🎀 🎀▏ 𝛔ƞℓɎ ᵭ୧ℓ୧†୧ ᎦᎮ𝐚ෆ 𝐚ƞᵭ Ꭶℓ𝐚ƞᵭ୧𝘳. 🐏🐏 🎀╥ħ𝐚ƞꝄ Ɏ𝛔𝐮 Ꭶ𝓦୧୧†ħ୧𝐚𝘳† ᰔᩚ

💘44❤‍🔥33💋21custom 539786144674484167911custom 53977987488122520339custom 54003761887513514249custom 53958746807730576058custom 54020919122219872468

27 Jan 2026, 13:04 UTC962 views175 reactionsread 15 August 2026
Photo

🎀🐏 ღұ ꝅוֹŋŋᎦܘŋ ᵱܘ Ꭶᵱܘꝅ୧וֹᎦ𝗁୧𝘳୧ יִ 🐏 🎀 я буду очень рад ему Артамיִ🤩 🤩𝐚ᓑŧ𝗁ܘ𝘳 ŧ𝗁୧ 𝓒𝗁𝐚𝘳𝐚𝓒ŧ୧𝘳 ∶ 🤩

❤‍🔥47custom 539786144674484167938💘29custom 539982082800514510011custom 539992586143036532111custom 540037618875135142411custom 539537052462694880010custom 539792931581804901010

17 Jan 2026, 21:22 UTC≈1,130 views165 reactionsread 15 August 2026
Photo

╘וֹŋꝅᎦ ŧܘ ෆұ 𝓒𝗁𝐚ŋŋ୧▏Ꭶ∶ くョ🤩 🤩₳𝘳ŧ 𝓒𝗁𝐚ŋŋ୧▏ ₍ ᵇ𝐚Ꭶוֹ𝓒 ⟭ 🤩 🤩𝓒𝗁𝐚ŋŋ୧▏ ẝܘ𝘳 ẝ𝘳וֹ୧ŋ𝙙Ꭶ 🤩🤩 🐏╤𝗁𝐚ŧʼᎦ וֹŧיִ ℱܘ𝘳 ŋܘധ ∶⟭ 🐏

❤‍🔥46💘40custom 539786144674484167924💔10custom 539587468077305760510custom 539779874881225203310custom 54003761887513514249👌8

17 Jan 2026, 21:17 UTC≈1,070 views267 reactionsread 15 August 2026
Photo

🎀🤩ⱲħØ 𝐚𝘳ᕦ 𝓨Ø𝙪Ɂ 🤩🎀 👍 ⨎𝐚ƞᎦ 🎀 💘 ⎣ί₭ᕦ ᵯ𝓨 ίƞ⨎Ø 🥹 💋𝘳 𝐚ᵯԺØᵯ 🥹 💊 ĐØ 𝓨Ø𝙪 ຟ𝐚ƞⱦ ⱦØ ƀᕦ ⨎𝘳ίᕦƞԺᎦ 💔 ଠا𝑑 բⲅוֹɘդ𝑑ş ᕉ 🥹 🎀 ᵳṛ⭘ෆ וֹ𝟆ᵳ⭘ ҟෆ 🥹🥹 🐏🐏▕ ⎣Ø√ᕦ 𝓨Ø𝙪 ᗉ。 კ 🤩🐏🐏

👍68💘63🍓38💋27💊14💔14custom 539786144674484167911custom 539792931581804901011

24 Aug 2025, 08:46 UTC≈2,460 views230 reactionsread 15 August 2026
Photo

🤩#𖧁୧ ღ𝐚rﺍØ𝑤 🤩❜⸴ḨʊʑØ" ⴰ🤩🤩 🐏 ⴰ ⸴ʹŢħęΥ ̷ ħę ⴰӀ🐏🤩🐏🤩🌟 😻🤩ׂ𝐧⃪i bᨡs𝓮 : ↿წ ΥⴰØⴰ 🎀🤩 ⴰ❜Ƚ𝐚𝜈 ﺍꜞᎦ𝔱 ̂ ˍ̂❜ⴰ ݊ ⸴𝟶ཥꜞդꜞØդ ₳␢Øʊ𝔱 ₥ęإⴰ‑ ᏕཥØꝄęꜞᎦħęręﺍØ𝜈ęr 🤩🖤

❤‍🔥83🍓45👍31custom 539786144674484167915custom 540024982651853622310💋9💊8🤗8

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

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.

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.

“๑︎ 忄ŋẝܘ ღ𝐚𝘳▏ܘധ 𖧁୧” (@marlowwwloverspokishere), 39 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/marlowwwloverspokishere.

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.