LIXIA PNP pinned a photo

Channel
LIXIA PNP
@LIXIApnp
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
21subscribers
+15 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004377164754 |
|---|---|
| Type | Channel |
| Username | @LIXIApnp |
| Created | Between 1 June 2026 and 28 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 3 October 2026 |
| On Telegram | t.me/LIXIApnp |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 17:58 | 21 | +2 |
| 24 Aug 2026, 09:35 | 19 | +2 |
| 15 Aug 2026, 20:57 | 17 | +11 |
| 12 Aug 2026, 19:48 | 6 | no change |
| 8 Aug 2026, 04:16 | 6 | first reading |
Engagement
15 posts held, back to 28 June 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 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 66.7% | |
| 👍 | 1 | 33.3% |
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 3 of the 15 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 28 June 2026 to 12 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
LIXIA PNP pinned a photo
Sorry again to all claimers
❤1
Cuz each batch arrive 100+pc ,sometimes until 200-300pcs And some claimers one time got many pc need to sort and post out,so I don't have time to put in new card sleeve one by one and also I don't have old card sleeve So pls pls pls request need new card sleeve if U worry that I post out without sleeve or use original card sleeve Sorry again🙇🏻🙇🏻 Cuz before this if the official website didn't provide card sleeve,mo…
👍1
Use singba card sleeve
All cardbox are buy from China,so Rm0.60 is the cost+shipping fee(from China), this pack fee not Inc "new card sleeve" So if need "new card sleeve",pls request when checkout postage,then I will calculate the pack fee of new card sleeve together 1 pack card sleeve Rm4(50pcs) Rm4÷50=Rm0.08
Choose Cardbox post out If U need new card sleeve,pls request when checkout postage cuz if the website is posted without card sleeve or with original sleeve,I will not put in the new card sleeve if didn't request Cardholder Inc card sleeve
Run out of new cardbox,so will use old cardbox until new cardbox arrive Old cardbox no charge pack fee
9 August 2026 SPX Express MY065095477328 - Adlina MY061437724758 - Muzfirah MY069655428668 - Athirah MY061496922058 - Nurtiza MY068312732558 - Chan Kah Qian MY063158658808 - xynnie MY061017123268 - Ashley MY061560608448 - Nur Rozzaidi MY063219061828 - John MY062012285508 - Andika MY061520677478 - wanieyushaa Done drop off all parcel!Pls record unboxing video when received🫶🏻 #LIXIApostage
4 August 2026 SPX Express MY066672197308 - Ain Azwa Mohd MY066063636478 - Yeris Liong MY065869475088 - Athirah MY061401457128 - Hani Ema MY061166276818 - Ismaa MY062026544438 - Yuni MY061797474158 - Chan Kah Qian MY066592583808 - Bay Qing Lin MY064127875218 - wanieyushaa MY069365871228 - Kong Yan Xin Done drop off all parcel!Pls record unboxing video when received🫶🏻 #LIXIApostage
27 July 2026 SPX Express MY069725138497 - Ismaa MY062495295727 - Andika Periyanto MY063842232457 - Muhammad Fitri Shah Bin Mohd Fadly Done drop off all parcel!Pls record unboxing video when received🫶🏻 #LIXIApostage
13 July 2026 SPX Express MY061271120897 - Muhammad Fitri Shah Bin Mohd Fadly MY064253300617 - Ruby MY068356534717 - Ismaa Done drop off all parcel!Pls record unboxing video when received🫶🏻 #LIXIApostage
❤1
Showing the 12 most recent of 15 posts we hold for @LIXIApnp. 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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“LIXIA PNP” (@LIXIApnp), 21 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/LIXIApnp.
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.