will extend cut off to 12pm since i sent the collection msgs pretty late 🙏 tysm!

Channel
keiji's cookies! 🍪
@keijiscookies
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,005subscribers
+9 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 | -1001537921803 |
|---|---|
| Type | Channel |
| Username | @keijiscookies |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/keijiscookies |
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 66% 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 |
|---|---|---|
| 15 Sept 2026, 10:21 | 1,005 | +12 |
| 7 Sept 2026, 01:54 | 993 | -5 |
| 30 Aug 2026, 07:43 | 998 | +1 |
| 22 Aug 2026, 21:08 | 997 | +3 |
| 16 Aug 2026, 07:34 | 994 | -2 |
| 8 Aug 2026, 00:34 | 996 | no change |
| 7 Aug 2026, 17:42 | 996 | first reading |
Engagement
16 posts held, back to 3 August 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
#arrival97 for the following! - alnst find your plus one animate fair - hq chimeke mascot vol 1-3 rerun - hq otemuchi nui class ver - hq itsunui - given exhibition encore mto goods - kinioto muzzle pop up shop - prsk epicks vol 27/28 (clpl) - prsk melopale mto* - personal comms *prsk melopale splits will be given out 15/8 mmu onwards instead, will be dming all split buyers next week about how to proceed w claims! a…
8/8 mmu post > suntec 2:45-3:30pm (exact location will be updated on the day itself) > cut off 8/8 (sat) 10am packing based on u/n commented only, not in comments = wont bring please comment username if opting tysm!! 🙇🏻 consol list; @xinnok @small_littleguy @mrnmnnt @chevooon @eichify @celete
updated claims! lf takers for the following! x3 uzuki natsuki x1 rion gaku
lf claimers for most of the designs for nuc premium pasha 🥹 rn ordering ~3 boxes only ><;; looking to order more if possible!!
#skdy #po skdy sunny afternoon goods po dec26 release rate*0.009, sp needed closeups in comments o7 comment item + qty if int!
#skdy #split skdy sunny afternoon chara photo collection split x4 splits, fujifilm material $5.94 ea, sp needed prior taro > rion > more do self bundle note for foil prior; - ea box will have one random foil replace normal, will give to buyers who claimed the chara at cost price - prior more of chara > more claims overall pls state chara + qty pls!
#hq #split [CLEARED] hq fuwa keychains (animate) split 3 (req) nov26 release, 50mm animate tkt; krkn $4.25 ea, sp needed comment chara + qty if int!
#hq #split [CLEARED] hq fuwa keychains (animate) split 2 nov26 release, 50mm animate tkt; krkn $4.25 ea, sp needed comment chara + qty if int!
#hq #split [CLEARED] hq fuwa keychains (animate) nov26 release, 50mm animate tkt; krkn $4.25 ea, sp needed comment chara + qty if int!
still lf takers for most of the nuc pasha designs!! 🥹🥹
hi! have updated claims for es v7 pashots (1st pic action, 2nd pic private), lf takers for the following! action; (confirmed 10 box) tori hokuto makoto mao tetora kanata hiiro mayoi nazuna hajime keito ibuki tsukasa sora yume private; (tentatively 5 box) tori hokuto makoto mao tetora kanata hiiro mika hinata yuuta kohaku adonis nazuna hajime souma tsukasa leo izumi natsume sora mama
Showing the 12 most recent of 16 posts we hold for @keijiscookies. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“keiji's cookies! 🍪” (@keijiscookies), 1,005 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/keijiscookies.
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.