Telegram RegisterThe public register of Telegram

Channel

الإعلام العسكري - كتائب القسام

@QaG_2

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

20,739subscribers

+363 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003835645774
TypeChannel
Username@QaG_2
Descriptionالقناة الاحتياطية2 لكتائب الشهيد عز الدين القسام
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/QaG_2

Topic

Politics & activism — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 5 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@QaG_2/243 · this entry13 Jul 2026, 18:28 UTC@ss_sisi/3691013 Jul 2026, 20:09 UTC1.001.7 hours
@QaG_2/245 · this entry14 Jul 2026, 11:00 UTC@ss_sisi/3691215 Jul 2026, 13:35 UTC1.0027 hours
@QaG_2/249 · this entry17 Jul 2026, 14:09 UTC@ss_sisi/3691617 Jul 2026, 15:01 UTC1.0052 minutes
@QaG_2/251 · this entry18 Jul 2026, 14:17 UTC@ss_sisi/3691718 Jul 2026, 17:43 UTC1.003.4 hours
@QaG_2/253 · this entry21 Jul 2026, 14:29 UTC@ss_sisi/3692021 Jul 2026, 17:42 UTC1.003.2 hours
@QaG_2/254 · this entry22 Jul 2026, 13:29 UTC@ss_sisi/3692122 Jul 2026, 14:39 UTC1.0070 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@ss_sisi11 (8/8 hand-verifiable sample passed)1.003.2 hoursthis entry (110)
@qassambrigades_RedirectionBot10 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (91)
@CLL7D9 (8/8 hand-verifiable sample passed)1.003.2 hoursthis entry (90)
@Qassamcircle7 (7/7 hand-verifiable sample passed)1.006.2 hoursthis entry (70)
@aqsaana7 (7/7 hand-verifiable sample passed)1.003 daysthis entry (70)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 13 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 6, the earliest publisher we hold is @Qassamcircle. That is a statement about our reading window, not a claim of authorship.

Views per post sit far above this size band

28,700 average views per post against 20,739 subscribers — an engagement rate of 138.5%. Across the 4,324 registered channels in the same cohort — 10,000–31,619 subscribers, posting mainly in Arabic — the middle half sit between 2.98% and 14.5%, with a median of 7.20%.

What this was computed from
Window30 days (13 July 2026 12 August 2026)
Posts measured23 of 23 published in the window (0 exact, 23 rounded by Telegram)
Views totalled660,820
Mature posts only138.5% over 23 posts read at least 24h after publication
Subscribers20,739 measured 12 August 2026
Cohortb10000:ara · 4,324 channels · p10 1.01% · p25 2.98% · p50 7.20% · p75 14.5% · p90 25.3%
Position in cohort99.884th percentile · 19.2× the cohort median
Uncertainty±0.077% of the figure, from Telegram’s rounding
Post languageArabic · 100.0%of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_mutual · clone_source · err_high, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 5 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

20,37620,73920,557.56 August 2026 — 20,376 subscribers6 August 2026 — 20,376 subscribers6 August 2026 — 20,476 subscribers7 August 2026 — 20,609 subscribers8 August 2026 — 20,673 subscribers9 August 2026 — 20,695 subscribers10 August 2026 — 20,717 subscribers11 August 2026 — 20,730 subscribers12 August 2026 — 20,739 subscribers6 August 202612 August 2026
9 measurements spanning 6 days, net +363. 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 20,322–20,793 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 01:5220,739+9
11 Aug 2026, 02:3320,730+13
10 Aug 2026, 02:1720,717+22
9 Aug 2026, 05:5120,695+22
8 Aug 2026, 07:1720,673+64
7 Aug 2026, 07:5020,609+133
6 Aug 2026, 08:4020,476+100
6 Aug 2026, 02:0620,376no change
6 Aug 2026, 00:1920,376first reading

Engagement

24 posts held, back to 13 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
139.8%
avg views ÷ 20,739 subscribers
Avg views / post
29,000
23 posts measured
Reaction rate
1.50%
reactions ÷ views · ER floor
Posts in window
23
of 24 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held24 (13 July 202610 August 2026)
Views total666,890
Reactions total10,011
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 23:19 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
66
Videos
133
Links
169

Lifetime counters from Telegram’s own channel header, read 12 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.

Video runtime
59m 08s
Average length
4m 56s

Measured directly from 12 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

10,011 reactions across 23 posts, in 4 distinct kinds. The most used accounts for 89.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8,90889.0%
👍5755.74%
🔥3343.34%
👌1941.94%

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 24 of the 24 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 10,537reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 24 most recent posts we hold, published 13 July 2026 to 10 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

10 Aug 2026, 15:02 UTC≈2,590 views286 reactionsread 12 August 2026
Forwarded from @AqmarTofanVideo

أَقمَارُ الطُّوْفَانْ الشهيد القائد الميداني/ معاذ كمال أبو سل ▫️كتيبة المقادمة (البريج) - لواء الوسطى تابعوا مرئيات شهداء القسام خلال معركة طوفان الأقصى عبر قناة أقمار الطوفان

258👌15👍8🔥5

9 Aug 2026, 14:45 UTC≈2,850 views347 reactionsread 12 August 2026
Forwarded from @AqmarTofanVideo

أَقمَارُ الطُّوْفَانْ الشهيد القائد القسامي/ إبراهيم أحمد البياري "أبو صهيب" ▫️قائد كتيبة الشهيد فوزي أبو القرع - لواء الشمال تابعوا مرئيات شهداء القسام خلال معركة طوفان الأقصى عبر قناة أقمار الطوفان

308🔥23👍11👌5

9 Aug 2026, 08:45 UTC≈3,500 views306 reactionsread 12 August 2026
Forwarded from @AqmarTofanVideo

أَقمَارُ الطُّوْفَانْ الشهيد القائد الميداني/ يوسف خليل دردونة ▫️كتيبة الشهيد عبد الرؤوف نبهان - لواء الشمال تابعوا مرئيات شهداء القسام خلال معركة طوفان الأقصى عبر قناة أقمار الطوفان

271👍22🔥9👌4

6 Aug 2026, 14:51 UTC≈5,880 views418 reactionsread 12 August 2026
Forwarded from @AqmarTofanVideo

أَقمَارُ الطُّوْفَانْ الشهيد القائد الميداني/ محمد فايز البرعي ▫️قائد التعبئة والتوجيه - لواء غزة تابعوا مرئيات شهداء القسام خلال معركة طوفان الأقصى عبر قناة أقمار الطوفان

362👍34🔥17👌5

2 Aug 2026, 08:45 UTC≈113,000 views523 reactionsread 12 August 2026
Photo

نحذر جمهورنا الكريم من الموقع الإلكتروني المُزيف الذي ينتحل هوية موقع كتائب القسام عبر العنوان التالي: ❌ www.alqassambrigade.com كما نحذر من التعامل مع أي بريد إلكتروني مزيف منبثق عن هذا الموقع وخصوصاً بريد جمع التبرعات بطريقة احتيالية تحت عنوان: ❌ fund@alqassambrigade.com ❌ info@alqassambrigade.com نؤكد لجمهورنا الكريم أن الموقع الرسمي والوحيد لكتائب القسام هو: ✅ www.alqassam.ps وأن البريد الإلكتروني الرسمي الو

422👍78👌21🔥2

1 Aug 2026, 13:51 UTC≈8,230 views380 reactionsread 12 August 2026
Forwarded from @AqmarTofanVideo

أَقمَارُ الطُّوْفَانْ الشهيد القائد الميداني/ مراد أحمد أبو مراد ▫️قائد سلاح الجو - لواء غزة تابعوا مرئيات شهداء القسام خلال معركة طوفان الأقصى عبر قناة أقمار الطوفان

338👍31🔥7👌4

31 Jul 2026, 14:32 UTC≈115,000 views601 reactionsread 12 August 2026
Photo

"فِي المُبْتَدَى وَالمُنْتَهَى هِيَ مَعَ اللهِ وَبِاللهِ وَتَحْتَ ظِلَالِ هَذَا المَنْهَجِ النَّبَوِيِّ الرَّبَّانِيِّ" الشهيد القائد الكبير/ إسماعيل هنية (أبو العبد) #طوفان_الأقصى الموقع الرسمي - كتائب القسام https://alqassam.ps

544👍28🔥19👌10

28 Jul 2026, 12:06 UTC≈9,710 views350 reactionsread 12 August 2026
Forwarded from @AqmarTofanVideo

أَقمَارُ الطُّوْفَانْ الشهيد القائد الميداني/ محمود محمد خضر ▫️كتيبة الشهيد عبد الرؤوف نبهان - لواء الشمال تابعوا مرئيات شهداء القسام خلال معركة طوفان الأقصى عبر قناة أقمار الطوفان

312👍25🔥8👌5

26 Jul 2026, 09:03 UTC≈9,960 views369 reactionsread 12 August 2026
Forwarded from @AqmarTofanVideo

أَقمَارُ الطُّوْفَانْ الشهيد القائد الميداني/ محمد أحمد البنا ▫️كتيبة المدفعية - لواء غزة تابعوا مرئيات شهداء القسام خلال معركة طوفان الأقصى عبر قناة أقمار الطوفان

336👍20🔥7👌6

24 Jul 2026, 10:57 UTC≈10,200 views359 reactionsread 12 August 2026

نهيب بكل أبناء شعبنا وعشائرنا وبشرفاء الأجهزة الأمنية أن يهبوا للدفاع عن مقدساتهم وأعراضهم وأرضهم، وألا يسمحوا لشذاذ الآفاق بالعربدة دون رادع، وليعلم الجميع أن معركة شعبنا الحقيقية مع الاحتلال هي في الضفة المحتلة، ونحن على ثقةٍ بأنها ستكون مفتاحاً للنصر الكامل على هذا المحتل النازي

325👍15🔥12👌7

24 Jul 2026, 10:57 UTC≈9,510 views346 reactionsread 12 August 2026

ليعلم هذا العدو المجرم أن للأقصى رجالاً تحميه، وأن الفلسطيني لا ينام على ضيم، وأن قلوب شبابنا تغلي وهم يرون الأقصى يُدنّس، والضفة تُهوّد وبيوتها تهدم وأراضيها تصادر، وغزة تُذبح من الوريد إلى الوريد، وأن تصعيد عدوانه لن يجلب عليه إلا الويلات

312👍14🔥14👌6

24 Jul 2026, 10:57 UTC≈9,990 views350 reactionsread 12 August 2026

تحية إجلالٍ وإكبارٍ إلى أهلنا المجاهدين في ضفة العياش وشبابها الثائرين الذين سددوا الضربات للاحتلال وتصدوا لقطعان مغتصبيه من نابلس إلى جنين والقدس، وانتقموا لأقصاهم الذي يئن تحت نير التدنيس من قبل أخسّ البشر

318👍13🔥11👌8

Showing the 12 most recent of 24 posts we hold for @QaG_2. 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.

Citation-graph rank

Citation-graph rank — 921 of 1,151,006entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

أقمار الطوفان الاحتياطية
@Alhajqasam · 86
8 posts
طلبة الحل العلاجي
@talabat_alhall_aleilaji · 734
4 posts
اناشيد فلسطينية و قسامية
@ftgh67 · 117
3 posts
خلف الخطوط
@october7_23 · 910
3 posts
نحن غزة 🔻
@we_are_gaza7 · 84
3 posts
بُرتقال يافاوي
@yafawii · 188
2 posts
المهيب الشامي
@abokataab600 · 8,465
1 post
أبـُو أنـس.🔻𓂆"
@abuanas105 · 2,086
1 post
أجنادُ القادةِ 💚
@ajnaad_alqadah · 2,388
1 post
الأخضر 💚
@Alakhdar1 · 189
1 post
حماس بلس
@alakhdar35 · 974
1 post
عزام
@alfurqan515 · 18
1 post
🇵🇸 وكالة أخبار بيت لحم 🇵🇸
@bethlehemnewss · 20,231
1 post
اللواء الشهيد محمد سعيد إيزدي- الحاج رمضان
@Hajramadan_ar · 509
1 post
الحركة الإسلامية الضفة الغربية
@hamaswestbank1 · 7,478
1 post
📟مراسل كتائب القسام📟
@Hussein_Al_Tayerr1 · 2,333
1 post
إيــــمَـان🔻
@imaneelhasnaoui · 190
1 post
MAJD.PS
@intefadaa · 168
1 post
الجبهة الداخلية الفلسطينية
@jabha_d · 7,325
1 post
أخبار أريحا
@JerichoNews · 14,466
1 post
وطن💚🔻
@mam4123 · 28
1 post
شاهد | الإعلام الحربي اليمني
@MilitaryMediaYVideos1 · 13,924
1 post
المَاجِدَة𓂆‏
@mmm2912 · 250
1 post
مصطفى || متابعات
@MostafaWhispers · 3,678
1 post
أخبار قلقيلية
@qalqilianewss · 14,868
1 post
كتائب العز القسامية 💚
@qassam3ez · 4,477
1 post
كتائب الشهيد عز الدين القسام
@QQO_D · 889
1 post
رثاء الشهداء (الإحتياطية)
@Rethaa_shohadaa · 3,151
1 post
حدس🔻
@SAAIko19 · 44
1 post
خواطر الشيخ الشعراوي
@sharaue · 1,493
1 post
سُـرج
@Surj231 · 1,049
1 post
Unmuted with Bint AL Maqawama
@unmutedd · 8
1 post
فِتْيَةُ الحَقّ🔻
@watan2moana05 · 73
1 post

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.

Mentions

Named by 4 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“الإعلام العسكري - كتائب القسام” (@QaG_2), 20,739 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/QaG_2.

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.