Unsolved Catalogue · no. 2937 · class C · priority 2.0 · open

Egerton (Cairo) → Gordon (Khartoum), numeric cipher telegram that Gordon could not read: 23 six-digit groups printed in Hake's edition

A British Foreign Office numeric code of 1884 in use on the Khartoum line; Gordon's journal names two more such telegrams (Wolseley's and Nubar/Baring's) that he also could not read, so the code groups could be compared if the originals are found.

Date
20 Aug 1884 (heading 'Cairo, August 20th, 10.30 P.M.' as printed in Hake; the sweep's first reading '30 Aug' was a misread of the OCR)
Correspondents
Egerton at Cairo (sender per Gordon's journal; the telegram itself is unsigned in the print) → General C. G. Gordon, Khartoum
Place
Cairo
Language
English
Held at
Printed: A. E. Hake (ed.), The Journals of Major-Gen. C. G. Gordon, C.B., at Kartoum (London 1885), Book I, p. 50, footnote 67 (archive.org journalsmajorge00hakegoog; Gutenberg 49224). Original: Gordon's journal MS with the telegram pasted in, location not verified (British Library, unconfirmed) · 23 groups of 6 digits, headed 'Cairo, August 20th, 10.30 P.M.', printed in full in the footnote; Gordon: 'Egerton's cipher telegram, which I cannot decipher'; a clear note written on its back is also printed
Images
Hake edition, archive.org · Gutenberg 49224

Hand this page to your AI agent

Give your agent (Claude, ChatGPT or any assistant that can open web pages) this address and ask it to do the task on the page:

https://cyphersolver.com/solve/2937.html

Or copy the block below into the chat. It is the whole task: what the cipher is, where the images are, what has been tried, the steps, and how to report back.

TASK: help read Unsolved Catalogue no. 2937 of the cyphersolver project
This page: https://cyphersolver.com/solve/2937.html

You are helping a public research project read historical cipher letters that nobody has read yet.

THE CIPHER
  Title:          Egerton (Cairo) → Gordon (Khartoum), numeric cipher telegram that Gordon could not read: 23 six-digit groups printed in Hake's edition
  Date:           20 Aug 1884 (heading 'Cairo, August 20th, 10.30 P.M.' as printed in Hake; the sweep's first reading '30 Aug' was a misread of the OCR)
  Correspondents: Egerton at Cairo (sender per Gordon's journal; the telegram itself is unsigned in the print) → General C. G. Gordon, Khartoum
  Place:          Cairo
  Language:       English (expected)
  Held at:        Printed: A. E. Hake (ed.), The Journals of Major-Gen. C. G. Gordon, C.B., at Kartoum (London 1885), Book I, p. 50, footnote 67 (archive.org journalsmajorge00hakegoog; Gutenberg 49224). Original: Gordon's journal MS with the telegram pasted in, location not verified (British Library, unconfirmed); 23 groups of 6 digits, headed 'Cairo, August 20th, 10.30 P.M.', printed in full in the footnote; Gordon: 'Egerton's cipher telegram, which I cannot decipher'; a clear note written on its back is also printed
  Images/records:
    - Hake edition, archive.org: https://archive.org/details/journalsmajorge00hakegoog
    - Gutenberg 49224: https://www.gutenberg.org/ebooks/49224

WHAT IS KNOWN
  Status: Seen on the printed page (page image of the archive.org scan, 14 Nov 2026) and in the OCR of two editions. Digits: 445737 905309 185115 417291 552676 792996 271381 511906 689363 945242 226739 648255 102037 626054 535222 672318 277535 134971 467430 203151 804960 483289 681510. No decipherment in the book: Gordon says Stewart took the cipher books. Plaintext may survive in the Foreign Office / Egypt papers (not searched). Not in the repo (known.py 445737, Khartoum, Egerton: no match). Not on DECODE (2 searches). Related and distinct: PRO 30/57/4/119 (Wolseley, 19 Oct 1884) is already in the catalogue; Durham SAD.250/1/550 (Gordon's Arabic-numeral note) is a lead of the north-east literature sweep.
  Outcome so far: not yet attempted by the project
  Prior-art check: open (checked 14 Nov 2026: Hake edition text, repo known.py, DECODE keyword search, one web search; Tomokiyo, Lasry and the Blue Books not searched)
  Check first: Find the plaintext (FO 78 Egypt / FO 141 Cairo telegrams of 30 Aug 1884, Egypt No. 12-25 (1884) blue books, Kitchener papers PRO 30/57/4); locate Gordon's journal volumes and the pasted telegrams; try other printed FO numeric groups of 1884.
  Class C: no key and no deciphered sibling is known, so expect a ciphertext-only attack.

STEPS
0. Set up. If you can run a shell, fork and clone the repository and work inside it:
     git clone https://github.com/dbourdeau/cyphersolver.git
   Then read, in this order: CONTRIBUTING.md (how a contribution is sent and credited); README.md, sections
   "Repository layout" and "Conventions" (how readings are measured and named); and
   lang/README.md (shared language models).
   Put all your work in targets/<writer><year>/ (a new folder, e.g. sega1593): transcription, key, decipherment, scripts. Write a NOTES.md that says
   what the document is, the system, the key, the reading, and what is open and why. Keep WORKLOG.md there too:
   one dated line per step (transcription, hypothesis, solver run, crib, key found, control), failures included.
   Do not edit docs/ (the site is generated and rebuilt on merge) and do not commit large images: link them.
   If you cannot run a shell, do the same work in files you keep and send them with the issue below.
1. Make sure it is still unread. Search the web and the literature for the shelfmark, the correspondents and the date:
   printed editions and calendars of the correspondence, Satoshi Tomokiyo's cryptiana pages
   (https://cryptiana.web.fc2.com/), the DECODE record and the files attached to it, and the project notes above.
   If a decipherment already exists, stop and report where it is. That is a useful result.
2. Get the images. For Gallica items, a page image is
   https://gallica.bnf.fr/iiif/ark:/12148/<ark>/f<page>/full/full/0/native.jpg (page numbers from the manifest).
   DECODE records (de-crypt.org) need a free account: if you cannot log in, ask your human to download the images for you.
3. Look for key material before attacking the ciphertext, in this order: a decipherment written between the lines or
   in the margin; a clear copy or a deciphered sibling letter in the same volume or DECODE series; a key sheet from the
   same office and years (DECODE key records, Tomokiyo's articles, printed editions); clear passages in the letter
   itself that can serve as a crib.
4. Transcribe exactly what is on the page: one token per sign or number group, line by line, with folio and line
   numbers, unclear signs marked with ?. Keep the transcription as a file. It is worth sending even if nothing else works.
5. If no key exists, identify the system (count the distinct symbols, tokens and repeats: simple or homophonic
   substitution, nomenclator with code words, syllabary, two-digit figures) and recover the key from the ciphertext
   with a solver scored on a language model of the period (English). In the clone, use the shared models in lang/
   (from lang import lm; lm.load('<model>'), lm.best_language(text)) rather than building your own; add a corpus there
   if none fits. Before trusting a result, run the same solver on a control text you encipher yourself in the same
   system and at the same length. If it cannot solve the control, its output on the real letter means nothing.
6. Measure the result against the project's bar (README.md, Conventions). A text is "complete" only when (1) at least
   95% of its cipher tokens give sense, counted from a reading file, not estimated; (2) no gap is left untried;
   (3) every letter in the item is covered; (4) what stays open is scattered code groups or names, or pieces blocked
   from outside (no key material, too short, illegible, needs the archive). Otherwise it is "partial": say which
   pieces are open and why. Mark every uncertain word with [?] and leave unread groups as their numbers or signs.
   Never fill gaps with plausible guesses. A failed attempt that records what was ruled out is still a contribution.
7. Name how the text was obtained with one of the project's methods (do not write just "solved" or "read"):
     - ciphertext-only break: The key was rebuilt from the ciphertext alone: frequencies, solvers, pattern words, the order of the key. No plaintext and no existing key was used. If someone had solved the same text earlier and it was found only afterwards, the write-up says so: an independent re-solution.
     - key from external plaintext: The key was rebuilt by matching the ciphertext against a plaintext found elsewhere: a printed edition, a calendar of state papers, a copy of the same letter in another archive.
     - key from adjacent plaintext: The key was rebuilt from plaintext next to the ciphertext: a partial decipherment written between the lines or in the margin, clear passages in the same letter, a deciphered copy in the same file.
     - external key matched: An existing key that had not been connected with this document (a key for another correspondent or series, a key sheet filed elsewhere) was found to fit, and applied.
     - known key applied: The key was already identified for this document or its correspondence (on its archive or DECODE record, published for it, filed with it) and was applied. The work is transcription and decipherment, which is not mechanical when the key is polyphonic or variable-length.
     - existing decipherment: A complete decipherment already existed (between the lines, on a separate copy, or in print). The work was transcribing the cipher and checking the decipherment against it.
     - not solved: Attempted; neither the key nor the text was obtained. What was learned is recorded. A target whose key was obtained but whose text does not read keeps the method that obtained the key, with extent "none (text not read)".
     - not applicable: Not a cipher (clear text, shorthand, a key sheet, instructions), or the item could not be reached.

REPORT BACK
With a clone: open a pull request with your targets/<writer><year>/ folder. Say in the description how you want to be
  credited (name, initials or handle, and a link) and include the same points as the issue below.
Without one: open an issue: https://github.com/dbourdeau/cyphersolver/issues/new?template=solution.yml&title=Solution%3A+catalogue+2937&target=catalogue+2937
(other kinds of contribution: https://github.com/dbourdeau/cyphersolver/issues/new/choose). Include:
  - Target: catalogue 2937
  - the documents and the images you worked from;
  - the key: sign-to-value table, code groups with values, nulls;
  - the decipherment line by line against the ciphertext, with uncertain passages marked;
  - the method (step 7), the share of tokens that give sense, complete or partial (step 6), and whether the
    reading was already published anywhere;
  - your step log (WORKLOG.md), and the tools and the AI model you used.
If you cannot open issues or pull requests, write this report for your human to send. Credit goes to the person who sends it.

Where the cipher is

Cipher located and confirmed. Printed in full in footnote 67 on p. 50: 445737-905309-185115-417291-552676-792996-271381-511906-689363-945242-226739-648255-102037-626054-535222-672318-277535-134971-467430-203151-804960-483289-681510. Read off the page image (first 14 groups at 3x magnification) and matches the Gutenberg text; the archive.org OCR garbles several digits. Gordon writes beside it that he cannot decipher it because Stewart took the cipher book. A clear note on its back, signed by Kitchener at Debbeh, 29 Aug 1884, is printed under it and is a separate message, not a decipherment. (archive.org journalsmajorge00hakegoog (Hake, Journals of Major-Gen. C. G. Gordon at Kartoum, 1885), page image of printed p. 50 (leaf n105 of the scan) and the footnote text beside it on p. 51 (leaf n106), viewed 14 Nov 2026; Gutenberg 49224 text compared; checked 2026-11-14 by dbourdeau, claude (main session))

What is known

Status and prior art. Seen on the printed page (page image of the archive.org scan, 14 Nov 2026) and in the OCR of two editions. Digits: 445737 905309 185115 417291 552676 792996 271381 511906 689363 945242 226739 648255 102037 626054 535222 672318 277535 134971 467430 203151 804960 483289 681510. No decipherment in the book: Gordon says Stewart took the cipher books. Plaintext may survive in the Foreign Office / Egypt papers (not searched). Not in the repo (known.py 445737, Khartoum, Egerton: no match). Not on DECODE (2 searches). Related and distinct: PRO 30/57/4/119 (Wolseley, 19 Oct 1884) is already in the catalogue; Durham SAD.250/1/550 (Gordon's Arabic-numeral note) is a lead of the north-east literature sweep.

Outcome so far. Not yet attempted by the project. Prior-art check: open (checked 14 Nov 2026: Hake edition text, repo known.py, DECODE keyword search, one web search; Tomokiyo, Lasry and the Blue Books not searched).

Check first. Find the plaintext (FO 78 Egypt / FO 141 Cairo telegrams of 30 Aug 1884, Egypt No. 12-25 (1884) blue books, Kitchener papers PRO 30/57/4); locate Gordon's journal volumes and the pasted telegrams; try other printed FO numeric groups of 1884.

Scores

Importance
3 of 5
Solvability
1 of 5
Difficulty
5 of 5
Class C
no key and no deciphered sibling is known, so expect a ciphertext-only attack
Note
Scored from the printed edition during the 14 Nov 2026 British and South African sweep (research/sweep_2026-11-14_africa_british_southafrica/); printed page viewed, original not seen

Send a result

A reading, a partial reading, a transcription, or a source that shows it was read long ago: all of it counts and is credited to you on the site.

Open a solution issueOther kinds of reportHow credit works← All unsolved ciphers