wanna play a game? @offzone2019hackquest

Channel
phdays2018hackquest
@phdays2018hackquest
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
186subscribers
-2 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 | -1001186571229 |
|---|---|
| Type | Channel |
| Username | @phdays2018hackquest |
| Created | Between 1 March 2018 and 27 April 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/phdays2018hackquest |
Topic
Hacking & security — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 |
|---|---|---|
| 30 Sept 2026, 14:02 | 186 | -1 |
| 19 Aug 2026, 11:38 | 187 | -1 |
| 7 Aug 2026, 07:16 | 188 | no change |
| 6 Aug 2026, 03:44 | 188 | first reading |
Engagement
20 posts held, back to 27 April 2018 — 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 20 posts for this entry, the most recent from 10 June 2019. An engagement rate over an empty window would be a number about nothing.
Recent posts
onemanteam, CSV and yerbol still does not activated their invition promo codes :( If you still went to phdays, please send pm to @dark8bit
Btw, current writeups: http://nightsite.biz/blog/19709-phdays-hackquest-wtiteup.html http://sqlulz.blogspot.com/2018/04/phdays-2018-rubik-writeup.html http://telegra.ph/hq-2018-writeup-04-30 http://telegra.ph/PHDays-HackQuest-WriteUp-05-01 https://forst.github.io/2018/04/30/phdays8_hackquest.html https://gist.github.com/fiercebrute/7328b3e62a80c433e5c9e6fea0864723 https://gist.github.com/paul-axe/1ed247ddda4bdfd08382…
All invitations are sent. If you don't get one, it's time to start worry. Today is the last day, when you can register your invition code on phdays.ticketforevent.com
8/15 writeups already recieved! Please hurry up, to get invition you need publish writeup. On any website, at any language, and also there is not necessary to write about all tasks, just about that were interesting to you 😝
Telegram alive, bot online, tasks work ok.
Telegram alive, but bot API still down :(
writeup can be written at any language (english or russian prefer)
1. paul_axe 4898 2. Beched 3048 3. AV1ct0r 2735 4. xymfrx 2480 5. alexeyst 1729 6. onemanteam 1670 7. Forst 1670 8. CSV 1415 9. koshcoca1ne 1356 10. fiercebrute 1356 11. yerbol 1230 12. mfocuz 1161 13. vladvis 1089 14. wrongsmith 1042 15. sms-system 1029
Regardless of telegram blocking we got such many members on contest. Thanks to all for participate! /scoreboard are frozzen now, but you still can solve tasks and submit tasks. Environment will work at least two weeks. Top15 places will receive invites to PHDays. To get invitation please make writeup, publish in to any place and send link to @dark8bit Top3 places will awarded on PHDays with prizes from wallarm
Hint for Rubik: It is 127.0.0.1:8080 and he knows how to execute commands in the docker.
Hint for audio.mp3: xxxxxxxx_xxxxx_xxxxxxx_x_xx_xxxx
Showing the 12 most recent of 20 posts we hold for @phdays2018hackquest. 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
Names
Channels on the register whose handles appear in this channel's posts.
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 30 September 2026 — this entry's latest reading, not the date you are reading this.
“phdays2018hackquest” (@phdays2018hackquest), 186 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/phdays2018hackquest.
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.