Telegram RegisterThe public register of Telegram
Telegram profile photo for Yulurve ˖ . ݁𝜗𝜚. ݁₊

Channel

Yulurve ˖ . ݁𝜗𝜚. ݁₊

@yulurve

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

1,034subscribers

+60 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002435884787
TypeChannel
Username@yulurve
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/yulurve

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.

Growth

9741,0341,0047 August 2026 — 974 subscribers8 August 2026 — 974 subscribers15 August 2026 — 983 subscribers24 August 2026 — 1,006 subscribers26 August 2026 — 1,005 subscribers29 August 2026 — 1,013 subscribers1 September 2026 — 1,022 subscribers4 September 2026 — 1,021 subscribers10 September 2026 — 1,026 subscribers13 September 2026 — 1,029 subscribers18 September 2026 — 1,034 subscribers7 August 202618 September 2026
11 measurements spanning 41 days, net +60. 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 965–1,043 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 06:171,034+5
13 Sept 2026, 15:221,029+3
10 Sept 2026, 03:001,026+5
4 Sept 2026, 17:161,021-1
1 Sept 2026, 11:551,022+9
29 Aug 2026, 18:381,013+8
26 Aug 2026, 17:231,005-1
24 Aug 2026, 03:241,006+23
15 Aug 2026, 17:34983+9
8 Aug 2026, 00:46974no change
7 Aug 2026, 18:25974first reading

Engagement

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

Reaction mix

11 reactions across 5 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
11100.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 6 of the 19 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 5 August 2026 to 7 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

7 Aug 2026, 15:01 UTC120 viewsread 8 August 2026
Forwarded from @heekeustorePhoto

sorry oot tapi anyone nak pc jay kucing ni tak for RM20? i claim from yulurve

Signed connie | bump if i dont reply

7 Aug 2026, 13:36 UTC247 viewsread 8 August 2026

someone want to pass jay ums pob engene ver rm 20, can dm @adrianadrew

Signed connie | bump if i dont reply

7 Aug 2026, 13:29 UTC256 viewsread 8 August 2026
Photo

can proceed alr and seller add this pcs also! still can add if ade yang nak

Signed nis

7 Aug 2026, 13:28 UTC238 viewsread 8 August 2026
Photo

bumpp this bulk, seller reduced price for the jay untaken pcs! and for the untaken pcs: - Rm10 reduced to Rm7 - Rm5 reduced to Rm3

Signed nis

7 Aug 2026, 13:19 UTC211 viewsread 8 August 2026
Photo

⋆。˚୨ #yulurveproof ୧˚。 𝐭𝐡𝐚𝐧𝐤𝐢𝐮𝐮 𝐟𝐨𝐫 𝐭𝐫𝐮𝐬𝐭𝐢𝐧𝐠 𝐮𝐬! 𖹭 ✧ vid condi in comment section

Signed nis

7 Aug 2026, 13:19 UTC203 viewsread 8 August 2026
Photo

⋆。˚୨ #yulurveproof #TSB07 ୧˚。 𝐭𝐡𝐚𝐧𝐤𝐢𝐮𝐮 𝐟𝐨𝐫 𝐭𝐫𝐮𝐬𝐭𝐢𝐧𝐠 𝐮𝐬! 🫶

Signed connie | bump if i dont reply

7 Aug 2026, 13:18 UTC173 views1 reactionsread 8 August 2026
Photo

⋆。˚୨ #yulurveproof #TSB06 ୧˚。 𝐭𝐡𝐚𝐧𝐤𝐢𝐮𝐮 𝐟𝐨𝐫 𝐭𝐫𝐮𝐬𝐭𝐢𝐧𝐠 𝐮𝐬! 🫶

1

Signed connie | bump if i dont reply

7 Aug 2026, 13:15 UTC178 viewsread 8 August 2026

𝒀𝑼𝑳𝑼𝑹𝑽𝑬 𝑷𝑨𝒀𝑴𝑬𝑵𝑻 𝑵𝑶𝑻𝑰𝑪𝑬 ⊹ᡣ𐭩₊⋆ #yulurvepayment #TSB07 [item price + admin fee rm1] slot 1 @sherryna02 - jaykewonsunki ✅ 💰 RM 100 + RM 1 @huneyyss - hoon ✅ 💰 RM 20 + RM 1 slot 2 @adrianadrew - jayhoon ✅ 💰 RM 40 + RM 1 @reenybae - riki ✅ 💰 RM 20 + RM 1 @ddeonhyun - sunoo ✅ 💰 RM 20 + RM 1 @lyunviey - jakewon ✅ 💰 RM 40 + RM 1 Kindly make your payment here (under min connie) ⟡ please done the payment asap ⟡ no backo

Signed connie | bump if i dont reply

7 Aug 2026, 13:13 UTC189 viewsread 8 August 2026

𝒀𝑼𝑳𝑼𝑹𝑽𝑬 𝑷𝑨𝒀𝑴𝑬𝑵𝑻 𝑵𝑶𝑻𝑰𝑪𝑬 ⊹ᡣ𐭩₊⋆ #yulurvepayment #TSB06 [item price + admin fee rm1] slot 1 @jaeyunwonz - jaykewon ✅ 💰 RM 33 + RM 1 @wldkqkr - riki ✅ 💰 RM 11 + RM 1 @peachyjjjae - hoon + keyring ✅ 💰 RM 14 + RM 1 @soraniey - sunoo 💰 RM 11 + RM 1 slot 2 @lyunviey - jaykesunwon ✅ 💰 RM 44 + RM 1 @adrianadrew - hoon + keyring ✅ 💰 RM 14 + RM 1 @reenybae - riki 💰 RM 11 + RM 1 slot 3 @glynnwong - jakewonki ✅ 💰 RM 33 + RM

Signed connie | bump if i dont reply

7 Aug 2026, 12:41 UTC216 views3 reactionsread 8 August 2026

all slots will proceed can claim if still want, price range is 20-25 not fixed payment probably next week

3

Signed connie | bump if i dont reply

7 Aug 2026, 12:03 UTC300 viewsread 8 August 2026
Photo

🇨🇳 | tsb wvs jp pob (pb ver) 💰 RM 20-25 each ❌❌❌ jungwon (slot 3 cant steal) ❌❌❌ jay ❌❌❌ jake ❌❌❌ sunghoon ❌❌✅ sunoo ❌❌✅ ni-ki - prio tie jaysunki, need all taken - price exc all fees - read tnc bfore claiming

Signed connie | bump if i dont reply

7 Aug 2026, 11:37 UTC225 viewsread 8 August 2026
Photo

𝒀𝑼𝑳𝑼𝑹𝑽𝑬 𝑷𝑨𝒀𝑴𝑬𝑵𝑻 𝑵𝑶𝑻𝑰𝑪𝑬 ⊹ᡣ𐭩₊⋆ #yulurvepayment [item price + admin fee + postage to wm] @Hudahalim33 - RM19 + RM1 + RM8 ✅ 🩵 tick @chickendumplingss - RM30 + RM1 + RM8 ✅ 💛 tick Kindly make your payment here (under min nis) ⟡ send me a screenshot of the receipt after your payment ⟡ please done the payment within 24 hours ⟡ no backout/cancellation once paid ⟡ dm me your mailing details

Signed nis

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

“Yulurve ˖ . ݁𝜗𝜚. ݁₊” (@yulurve), 1,034 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/yulurve.

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.