Channel
@ructfe
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
440subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001002554185 |
|---|---|
| Type | Channel |
| Username | @ructfe |
| Description | RuCTFE is an annual online international challenge in the information security that was held annually from 2009 to 2020. Now it is a part of RuCTF event, so please join @RuCTF channel |
| Created | 14 October 2015 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ructfe |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 21:31 | 440 | no change |
| 6 Aug 2026, 21:18 | 440 | first reading |
19 posts held, back to 21 May 2021 — 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 pageof 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 19 posts for this entry, the most recent from 2 April 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
16 reactions across 4 posts, in 9 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 4 | 25.0% | |
| 🤩 | 4 | 25.0% | |
| 👍 | 2 | 12.5% | |
| 👎 | 1 | 6.25% | |
| 💩 | 1 | 6.25% | |
| 🔥 | 1 | 6.25% | |
| 😱 | 1 | 6.25% | |
| 🤔 | 1 | 6.25% | |
| 🥰 | 1 | 6.25% |
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 4 of the 19 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 16reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 21 May 2021 to 2 April 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Alright, this was a joke. There is no RuCTF Edu. However, RuCTF is still going to take place online on April 24th! The registration will be opened soon. And, from now on, RuCTF will include both of our A/D competitions — the online one as well as the offline competition for top student teams, so please follow @RuCTF. And what about @TRuCTF? We'll see.....
🤔1
Photo, posted without a caption
😁3
Channel name was changed to «RuCTFE [DEPRECATED]»
Time for some news On April 24th we're making RuCTF — an online team competition, available for anybody. Previously we called it "RuCTFE" ('E' for Extended) but now we decided to change the name, because it seems like no one can really tell the difference between these two except for our developers themselves. From now on, the primary and main competition is called RuCTF. This fall, best teams of RuCTF will be able…
🤩4🔥1😁1😱1
CBS@CTF:~/$ cd .. Permission denied: stay the fuck home! CBS@CTF:~/$ date Sun 06 Feb 2022 10:00:00 UTC CBS@CTF:~/$ cat chats.txt 🇷🇺 @cbsctf 🇺🇸 @cbsctf_en CBS@CTF:~/$ cat announcement.txt Two years have passed as the world is wearing medical masks. The influx of covid waves will be the envy of any coast, and there are so many strains of the virus that you can assemble a platinum collection of the Greek alphabet. There…
👍2👎1💩1🥰1
Greetings from Abu-Dabi! Here, our Dev team is making HITB PRO CTF which will last for next 29 hours. You can visit the scoreboard to support playing teams or watch a cool game visualization on https://viz.ctf.hitb.org/
Sorry to say that, but we are rescheduling RuCTFE to spring 2022. This winter, we got trapped by Father Frost, thus, RuCTFE 2022 will come next spring promising to be cool and fun. Take care and stay tuned!
Once upon a time, there was a competition... This year, RuCTFE takes place on 19th December. Make sure you've made that Sunday free for some good old A/D. The game will show, who's the best at Going We Know Not Whither and Fetching We Know Not What. Want to become our partner or sponsor? Contact @AAAlexeev
We’ll also count votes from Twitter: https://twitter.com/RuCTFE/status/1450816613968658435
RuCTFE [DEPRECATED] pinned «This year RuCTFE will be again held in the end of December. Together, let's choose the lesser of two evils — it's either having our competition crossed with hxp CTF or playing it at the Christmas table. Please, choose the date:»
This year RuCTFE will be again held in the end of December. Together, let's choose the lesser of two evils — it's either having our competition crossed with hxp CTF or playing it at the Christmas table. Please, choose the date:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Let RuCTF 2021 be! After a long time of clearing the details and getting things done, we shall now announce: RuCTF 2021 will take place online on October, 3. Starting at 12:00 PM YEKT (7:00 AM UTC), the game takes 8 hours non-stop. A new set of invites (like the old ones, just with some additional details) will arrive this weekend, network test configurations are coming on 24.09. And for anybody who doesn't partic…
Showing the 12 most recent of 19 posts we hold for @ructfe. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
This year RuCTFE will be again held in the end of December. Together, let's choose the lesser of two evils — it's either having our competition crossed with hxp CTF or playing it at the Christmas table. Please, choose the date:
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 21 May 2021 to 2 April 2022. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 709,671 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“RuCTFE [DEPRECATED]” (@ructfe), 440 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/ructfe.
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.