Q15, run 2026-11-04-1824-haiku

← back to the run

What was Halden Bank's rating on 1 January 2026?

Tests: Time: the downgrade came later in 2026.

Expected: rating = A-

✅ R1 csv run 1 graded by code

A-. Halden Bank AG (E10) was rated A- (A26) until the 2026-04-15 downgrade to BBB+ (A27). The E17 duplicate has no rating records.

JSON: {"rating": "A-"}

✅ R1 csv run 2 graded by code

A-. A26 assigned A- and the downgrade to BBB+ (A27) came on 2026-04-15, so the rating on 1 Jan 2026 was still A-.

JSON: {"rating": "A-"}

✅ R1 csv run 3 graded by code

A-. E10's A- from A26 (2023-05-01) was still in place on 1 Jan 2026; the downgrade to BBB+ came in A27 (2026-04-15). E17 is the same LEI but has no ratings.

JSON: {"rating": "A-"}

✅ R1 csv run 4 graded by code

A-. The 2023 rating (A26) was unchanged until the downgrade to BBB+ on 2026-04-15 (A27).

JSON: {"rating": "A-"}

✅ R1 csv run 5 graded by code

A-. E10's rating on 1 January 2026 was A-, from A26, before A27 downgraded it to BBB+ in April 2026. (E17 has the same LEI but no ratings.)

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 1 graded by code

A-. Halden Bank is E10 (E17 has the same LEI), and its A- from A26 holds until the 2026-04-15 downgrade (A27).

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 2 graded by code

A-. E10's rating on 2026-01-01 was the assigned A- (A26), since the downgrade to BBB+ came on 2026-04-15 (A27).

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 3 graded by code

A-. The downgrade to BBB+ came on 2026-04-15 (A27), which is after 2026-01-01.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 4 graded by code

A-.
E10's latest action before 1 Jan 2026 is A26 (A-, 2023-05-01); the downgrade to BBB+ (A27) is dated 2026-04-15.

JSON: {"rating": "A-"}

✅ R5 csv+ontology run 5 graded by code

A-. E10's A27 downgrade to BBB+ is dated 2026-04-15, after 1 Jan 2026.

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 1 graded by code

A-. E10 (Halden Bank AG, which E17 duplicates) was rated A- under A26 until the downgrade A27 on 2026-04-15.

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 2 graded by code

A-
E10 and E17 share an LEI. A26 (A-) was in force on 1 Jan 2026, before A27 (2026-04-15).

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 3 graded by code

A-. Halden Bank's 2026 downgrade to BBB+ (A27) came on 2026-04-15, after 1 January 2026.

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 4 graded by code

A-
E10 (Halden Bank AG) held A26 (A-) until A27 (BBB+, 2026-04-15), so on 1 Jan 2026 it was A-. E17 is the same entity with no ratings of its own.

JSON: {"rating": "A-"}

✅ R8 csv+axioms run 5 graded by code

A-. Halden Bank (E10) was A- from A26, which stayed in force until the downgrade to BBB+ on 2026-04-15 (A27). E17 is the same entity.

JSON: {"rating": "A-"}

✅ R9 csv+axioms+markdown run 1 graded by code

A-. Halden Bank (E10, same LEI as E17) was A- from 2023-05-01 (A26) until its downgrade to BBB+ on 2026-04-15 (A27).

JSON: {"rating": "A-"}

✅ R9 csv+axioms+markdown run 2 graded by code

A-. E10's latest action on or before 2026-01-01 is A26 (AS, A-); the downgrade A27 came later.

JSON: {"rating": "A-"}

✅ R9 csv+axioms+markdown run 3 graded by code

A-. On 1 Jan 2026 the latest action is A26 (A-, 2023-05-01). The downgrade to BBB+ (A27) came on 2026-04-15, which is later.

JSON: {"rating": "A-"}

✅ R9 csv+axioms+markdown run 4 graded by code

A-. A26 (AS, A-) holds until A27 (DG to BBB+) on 2026-04-15. E17 is the same entity as E10 (same LEI).

JSON: {"rating": "A-"}

✅ R9 csv+axioms+markdown run 5 graded by code

A-
The 2026 downgrade to BBB+ (A27) comes after 2026-01-01, so the rating then was A- (A26).

JSON: {"rating": "A-"}