Unsolved Catalogue · no. 2570 · class A · priority 5.5 · open

'Chemnitz' (Nuremberg) to Gustav II Adolf: German despatches of Nov-Dec 1631 with number-and-letter cipher, some passages without decipherment

A 1631 German-language number cipher whose deciphered letter (image 57) sits in the same volume, which gives a crib for the bare passages on 55 and 56, about the movements of Wallenstein and the contributions of Nuremberg.

Date
5 Nov - 14 Dec 1631 (letters dated 5 Nov, 7 Dec and 14 Dec 1631)
Correspondents
signature read as '...Chemnitz' (first name not read; a Swedish agent writing from Nuremberg) -> King Gustav II Adolf
Place
Nuremberg ('Datum Nürnberg den 7 Xbris Ao 1631'); 55/57 letter from 'Mainz 14 Dec 1631' on the cover of image 59 (the cover's place not checked against the letter)
Language
German
Held at
Riksarkivet, Skrivelser till konungen, SE/RA/1133/1133.07/4 (C), image series R0000624, images 55-59 · R0000624 image 55 (one leaf): a 6-line passage of dotted numbers with letters (m, pf, q, gl) at the foot of the German text, no gloss; image 56 left page: a 7-line passage, no gloss, under a letter of Wallenstein's movements ('Friedland', 'Würzburg'), dated Nuremberg 7 Dec 1631; image 58: 5 Nov 1631 letter with a passage that has small plaintext words above some groups, and a 7 Dec postscript in clear; image 57: a letter written almost wholly in number-and-letter groups with a German decipherment written between the lines (glossed). So the glossed sibling and the bare passages are in the same hand and volume
Images
Riksarkivet viewer, image 55 · image 56 · image 57 (glossed)

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/2570.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. 2570 of the cyphersolver project
This page: https://cyphersolver.com/solve/2570.html

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

THE CIPHER
  Title:          'Chemnitz' (Nuremberg) to Gustav II Adolf: German despatches of Nov-Dec 1631 with number-and-letter cipher, some passages without decipherment
  Date:           5 Nov - 14 Dec 1631 (letters dated 5 Nov, 7 Dec and 14 Dec 1631)
  Correspondents: signature read as '...Chemnitz' (first name not read; a Swedish agent writing from Nuremberg) -> King Gustav II Adolf
  Place:          Nuremberg ('Datum Nürnberg den 7 Xbris Ao 1631'); 55/57 letter from 'Mainz 14 Dec 1631' on the cover of image 59 (the cover's place not checked against the letter)
  Language:       German (expected)
  Held at:        Riksarkivet, Skrivelser till konungen, SE/RA/1133/1133.07/4 (C), image series R0000624, images 55-59; R0000624 image 55 (one leaf): a 6-line passage of dotted numbers with letters (m, pf, q, gl) at the foot of the German text, no gloss; image 56 left page: a 7-line passage, no gloss, under a letter of Wallenstein's movements ('Friedland', 'Würzburg'), dated Nuremberg 7 Dec 1631; image 58: 5 Nov 1631 letter with a passage that has small plaintext words above some groups, and a 7 Dec postscript in clear; image 57: a letter written almost wholly in number-and-letter groups with a German decipherment written between the lines (glossed). So the glossed sibling and the bare passages are in the same hand and volume
  Images/records:
    - Riksarkivet viewer, image 55: https://sok.riksarkivet.se/bildvisning/R0000624_00055
    - image 56: https://sok.riksarkivet.se/bildvisning/R0000624_00056
    - image 57 (glossed): https://sok.riksarkivet.se/bildvisning/R0000624_00057

WHAT IS KNOWN
  Status: Viewed 13 Nov 2026: images 54-59 at 700 px, 56 and 57 at 1700 px, 58 at 1800 px. Nomenclator of 2-digit numbers with letters m, pf and others, German context. Passages on 55 and 56 show no decipherment at that size; the top-64 window sheet of this volume was the only screening, so more passages may lie elsewhere in the volume. known.py on R0000624, 1133.07/4 and 'Chemnitz': no hit. Lead, no vetting block: no edition opened (Swedish despatches from Nuremberg of 1631 may be printed in the Gustav Adolf correspondence editions; not searched). Work in targets/chemnitz1631 (PR #539, Brice Dudout, 13 Nov 2026): writer Martin Chemnitz (contributor's identification), key rebuilt from the image 57 glosses, images 55-56 read in part (68 of 89 words sure); in progress, lead stays open.
  Outcome so far: not yet attempted by the project
  Prior-art check: known.py: no hit. DECODE, Tomokiyo, Lasry and editions not searched for this item.
  Check first: Identify the writer (the signature after 'Undertänigster gehorsamer Diener' ends in '-mnitz'); look for a printed edition of his 1631 despatches; transcribe image 57's gloss to build the table and read 55 and 56.
  Class A: a sibling letter with a decipherment is in the same volume or series, so matching it is the first move.
  Project notes (read these before anything else; they record what was tried and ruled out): https://github.com/dbourdeau/cyphersolver/blob/main/targets/chemnitz1631/NOTES.md

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); targets/chemnitz1631/NOTES.md (everything
   already tried on this cipher, with the files it used); and lang/README.md (shared language models).
   Put all your work in targets/chemnitz1631/: transcription, key, decipherment, scripts. Add your findings to its NOTES.md
   under a dated heading, without rewriting what is there. 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 (German). 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/chemnitz1631/ 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+2570&target=catalogue+2570
(other kinds of contribution: https://github.com/dbourdeau/cyphersolver/issues/new/choose). Include:
  - Target: catalogue 2570
  - 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. Dot-separated 1-2 digit numbers with letters; on 55 and 56 nothing between the lines or in the margin. Image 57 is glossed word by word, so the system is deciphered on a sibling leaf, not on these two. (Riksarkivet R0000624 images 55, 56 and 57 (img/rik_R0000624_00055.jpg, 00056.jpg, 00057.jpg, Referer route), image 56 viewed 16 Nov 2026; the 13 Nov brief-test vetting (research/vetting_2026-11-13_brief_test/vetting.json) opened 55-57 at 1800 px.; checked 2026-11-16 by claude session 16 Nov 2026 (Claude Opus 5.5), wave 17 vetting)

What is known

Status and prior art. Viewed 13 Nov 2026: images 54-59 at 700 px, 56 and 57 at 1700 px, 58 at 1800 px. Nomenclator of 2-digit numbers with letters m, pf and others, German context. Passages on 55 and 56 show no decipherment at that size; the top-64 window sheet of this volume was the only screening, so more passages may lie elsewhere in the volume. known.py on R0000624, 1133.07/4 and 'Chemnitz': no hit. Lead, no vetting block: no edition opened (Swedish despatches from Nuremberg of 1631 may be printed in the Gustav Adolf correspondence editions; not searched). Work in targets/chemnitz1631 (PR #539, Brice Dudout, 13 Nov 2026): writer Martin Chemnitz (contributor's identification), key rebuilt from the image 57 glosses, images 55-56 read in part (68 of 89 words sure); in progress, lead stays open.

Outcome so far. Not yet attempted by the project. Prior-art check: known.py: no hit. DECODE, Tomokiyo, Lasry and editions not searched for this item..

Check first. Identify the writer (the signature after 'Undertänigster gehorsamer Diener' ends in '-mnitz'); look for a printed edition of his 1631 despatches; transcribe image 57's gloss to build the table and read 55 and 56.

Scores

Importance
2 of 5
Solvability
4 of 5
Difficulty
2 of 5
Class A
a sibling letter with a decipherment is in the same volume or series, so matching it is the first move
Note
Scored from the scan during the 13 Nov 2026 Nordic paging sweep (research/sweep_2026-11-13_nordic_paging/); viewed

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