Telegram RegisterThe public register of Telegram
Telegram profile photo for lululalainsights

Channel

lululalainsights

@lululaladick

2 usernames

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

2subscribers

-2,342 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002345480705
TypeChannel
Usernames@lululaladick @lululalaInsights
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 September 2026
Measurements held14
Confirmed unchanged2 times, most recently 8 September 2026
On Telegramt.me/lululaladick

Growth

22,3821,1926 August 2026 — 2,344 subscribers6 August 2026 — 2,344 subscribers6 August 2026 — 2,342 subscribers9 August 2026 — 2,341 subscribers16 August 2026 — 2,342 subscribers19 August 2026 — 2,346 subscribers23 August 2026 — 2,347 subscribers26 August 2026 — 2,362 subscribers29 August 2026 — 2,365 subscribers1 September 2026 — 2,382 subscribers2 September 2026 — 2,376 subscribers3 September 2026 — 2,376 subscribers3 September 2026 — 2,377 subscribers4 September 2026 — 2 subscribers6 August 20264 September 2026
14 measurements spanning 30 days, net -2,342. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 16:362-2,375
3 Sept 2026, 18:562,377+1
3 Sept 2026, 00:002,376no change
2 Sept 2026, 23:452,376-6
1 Sept 2026, 04:472,382+17
29 Aug 2026, 00:382,365+3
26 Aug 2026, 10:112,362+15
23 Aug 2026, 05:562,347+1
19 Aug 2026, 20:472,346+4
16 Aug 2026, 17:152,342+1
9 Aug 2026, 18:152,341-1
6 Aug 2026, 19:362,342-2
6 Aug 2026, 05:492,344no change
6 Aug 2026, 03:322,344first reading

Engagement

52 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 3 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22852.6%
avg views ÷ 2 subscribers
Avg views / post
457
19 posts measured
Reaction rate
0.39%
reactions ÷ views · ER floor
Posts in window
19
of 52 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 6 of 19 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held52 (5 August 20262 September 2026)
Views total8,684
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 00:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
31s
Average length
31s

Measured directly from 1 video 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.

Reaction mix

28 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 67.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1967.9%
😁310.7%
🤣310.7%
🤯27.14%
13.57%

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 23 of the 52 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 51 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

2 Sept 2026, 21:29 UTC286 views1 reactionsread 3 September 2026
Photo

엄... TJR 탑승하고 바이럴 더 되는 느낌이네

1

2 Sept 2026, 16:01 UTC406 viewsread 3 September 2026
Forwarded from @crypt0_seaPhoto

https://x.com/RuneCrypto_/status/2095171519768940795 클로드로 과장해서 스토리써달라했다네요

2 Sept 2026, 15:36 UTC496 views3 reactionsread 3 September 2026

솔캣 이 새끼들 한자리 결국 차지했네 ㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋ

😁3

2 Sept 2026, 15:36 UTC365 viewsread 3 September 2026
Forwarded from @bitethebulletkrPhoto

솔라나 네팔 구호 모금 종료 총 모금액 166,946.50 좋은 의도와는 별개로 개같이 사기 싫은 것들만 덕지덕지 붙음 https://x.com/solana/status/2095173372158394780

2 Sept 2026, 15:33 UTC358 viewsread 3 September 2026
Forwarded from @gensencoinPhoto

전) 멀티코인 Kyle 백팩 이사회 합류

2 Sept 2026, 15:12 UTC452 viewsread 3 September 2026

그건 그렇고 FOMO 맛탱이갔는데 빠른 복구좀요 ㅠㅜ 얼마나 핫한거야 🥳🥳🥳🥳🥳🥳🥳🥳🥳

2 Sept 2026, 15:12 UTC290 views1 reactionsread 3 September 2026

쉽게 정리 오늘 로빈후드 체인에서 $JINQIAN이라는 밈코인이 떴는데, 차트보다 뒤에 깔린 스토리가 훨씬 재밌음. JINQIAN은 중국어로 "돈"이고 버섯 컨셉인데, 이게 $FAMI랑 페어로 묶여 있음. FAMI는 나스닥에 상장된 중국 버섯 회사 Farmmi 주식을 토큰화한 거고, 심지어 JINQIAN이라는 이름 자체가 Farmmi 실제 제품명에서 나온 거임. 아무 밈이랑 아무 주식을 갖다 붙인 게 아니라 그 회사에서 나온 밈을 그 회사 주식에 붙인 거라 앞뒤가 맞음. 여기서 왜 시끄러워졌냐면, 8월 31일에 루네가 이런 아이디어를 공개로 던졌음. 나스닥 잡주를 사서 로빈후드 체인에 토큰화하고, 거기에 밈코인을 직접 페어링해서 크립토 유동성으로 수요를 만든다는 거. 밈코인이 사지면 페어에 묶인 주식 토큰 수요가 늘고, 민트/리딤으로 그

1

2 Sept 2026, 14:44 UTC242 viewsread 3 September 2026
Forwarded from @bitethebulletkrPhoto

https://x.com/RuneCrypto_/status/2094474650541543914 @RuneCrypto_ 의 아이디어로 시작된 토큰화 주식 페어링으로 공매도 터뜨리기 전략이 실제로 로빈후드체인에서 일어나고 있는 중. 현재 나스닥에 상장된 FAMI 주식은 200%를 왔다갔다하고 있음

2 Sept 2026, 14:40 UTC683 viewsread 3 September 2026

근데 생각해보면 솔라나때 펌프펀이 본딩보내면서 영구적으로 LP에 잠기게되는 솔라나의 숫자가 어마어마했는데 주식도 페어가 존나게 많지만 토큰화 된 주식은 영구적으로 잠기는거임? 그럼 시총적은데 많이 쓰이게되는 페어는 락업 효과가 되는건가? 진짜 궁금해서 물어봄 아시는분?

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

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 2 registered channels — 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.

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 4 September 2026 — this entry's latest reading, not the date you are reading this.

“lululalainsights” (@lululaladick), 2 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/lululaladick.

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.