Telegram RegisterThe public register of Telegram
Telegram profile photo for HeapCheapTrips

Supergroup

HeapCheapTrips

@heapcheaptripss

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

1,551members

+46 since we began measuring on 7 August 2026

241 online right now

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

Register entry

Telegram ID-1001612777639
TypeSupergroup
Username@heapcheaptripss
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live4 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/heapcheaptripss

Topic

Travel — 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 27 September 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 the other topics.

Growth

1,5051,5511,5287 August 2026 — 1,505 members8 August 2026 — 1,507 members11 August 2026 — 1,509 members15 August 2026 — 1,520 members17 August 2026 — 1,524 members20 August 2026 — 1,533 members24 August 2026 — 1,538 members27 August 2026 — 1,541 members30 August 2026 — 1,545 members2 September 2026 — 1,518 members6 September 2026 — 1,531 members10 September 2026 — 1,534 members14 September 2026 — 1,537 members19 September 2026 — 1,527 members27 September 2026 — 1,527 members29 September 2026 — 1,540 members6 October 2026 — 1,525 members12 October 2026 — 1,526 members15 October 2026 — 1,527 members19 October 2026 — 1,535 members22 October 2026 — 1,534 members25 October 2026 — 1,542 members29 October 2026 — 1,544 members1 November 2026 — 1,548 members4 November 2026 — 1,551 members7 August 20264 November 2026
25 measurements spanning 89 days, net +46. 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 1,498–1,558 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
4 Nov 2026, 21:261,551+3
1 Nov 2026, 12:051,548+4
29 Oct 2026, 09:381,544+2
25 Oct 2026, 23:511,542+8
22 Oct 2026, 19:251,534-1
19 Oct 2026, 09:561,535+8
15 Oct 2026, 23:181,527+1
12 Oct 2026, 19:491,526+1
6 Oct 2026, 04:391,525-15
29 Sept 2026, 08:171,540+13
27 Sept 2026, 16:261,527no change
19 Sept 2026, 03:381,527-10
14 Sept 2026, 11:151,537+3
10 Sept 2026, 23:171,534+3
6 Sept 2026, 09:211,531+13
2 Sept 2026, 06:371,518-27
30 Aug 2026, 08:051,545+4
27 Aug 2026, 04:461,541+3
24 Aug 2026, 03:041,538+5
20 Aug 2026, 13:521,533first 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.

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

“HeapCheapTrips” (@heapcheaptripss), 1,551 members as measured 4 November 2026. Telegram Register, tgregister.com/channel/heapcheaptripss.

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.