Telegram RegisterThe public register of Telegram
Telegram profile photo for HKUSPACE Swap科區

Supergroup

HKUSPACE Swap科區

@hkuspaceswap

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

1,293members

+642 since we began measuring on 10 September 2026

74 online right now

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

Register entry

Telegram ID-1004492603292
TypeSupergroup
Username@hkuspaceswap
DescriptionNon JUPAS資訊頻道 @nonjupas_channel Non JUPAS派位記錄 @nonjupasspreadsheet Non Jupas 討論區 @nonjupas 太空圍爐取暖區 @hkuspaceastronauts 太空社科 @spacesocsci
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 October 2026
Last confirmed live2 October 2026
Measurements held4
On Telegramt.me/hkuspaceswap

Topic

Education — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 80% 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

6511,29397210 September 2026 — 651 members12 September 2026 — 762 members30 September 2026 — 1,293 members2 October 2026 — 1,293 members10 September 20262 October 2026
4 measurements spanning 22 days, net +642. 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 555–1,389 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
2 Oct 2026, 03:441,293no change
30 Sept 2026, 15:371,293+531
12 Sept 2026, 06:22762+111
10 Sept 2026, 14:47651first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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

“HKUSPACE Swap科區” (@hkuspaceswap), 1,293 members as measured 2 October 2026. Telegram Register, tgregister.com/channel/hkuspaceswap.

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.