Q15, run 2026-11-04-1644-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 (E10) was rated A- from 2023-05-01 (A26), and was downgraded to BBB+ only on 2026-04-15 (A27).

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

✅ R1 csv run 2 graded by code

A-. E10 (Halden Bank) was A- until its cut to BBB+ on 2026-04-15 (A27). E17 has the same LEI and no rating actions.

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

✅ R1 csv run 3 graded by code

A-. A26 (A-) was in effect until A27 downgraded E10 on 2026-04-15.

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

✅ R1 csv run 4 graded by code

A-. A26 (2023-05-01) assigned A-, and the downgrade to BBB+ came later, in A27 (2026-04-15). E17 (same LEI as E10) carries no rating.

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

✅ R1 csv run 5 graded by code

A-. The downgrade to BBB+ is dated 2026-04-15 (A27), which is after 1 Jan 2026.

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

✅ R2 rdf run 1 graded by code

A-
E10 (Halden Bank AG) was A- from A26 (2023-05-01) until the downgrade to BBB+ in A27 (2026-04-15). E17 (also "Halden Bank") has no ratings.

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

✅ R2 rdf run 2 graded by code

A-. A26 (AS A-, 2023-05-01) was in effect until A27 (DG BBB+, 2026-04-15).

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

✅ R2 rdf run 3 graded by code

A-. Halden Bank AG (E10) was A- from A26 (2023-05-01) until its April 2026 downgrade (A27). E17 has no ratings.

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

✅ R2 rdf run 4 graded by code

A-. E10's A-rating (A26, 2023-05-01) was still in force until the 2026-04-15 downgrade to BBB+ (A27). E17 has the same LEI but no ratings.

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

✅ R2 rdf run 5 graded by code

A-
I take "Halden Bank" to mean E10, which had A- until its downgrade to BBB+ on 2026-04-15 (A26, A27). E17 is also named "Halden Bank" but is unrated and shares E10's LEI.

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

✅ R6 rdf+ontology run 1 graded by code

A-. A26 (2023-05-01) is the latest action before 2026-01-01; the downgrade to BBB+ (A27) came on 2026-04-15.

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

✅ R6 rdf+ontology run 2 graded by code

A-.
E10's A26 (A-, 2023-05-01) held until A27 (2026-04-15).

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

✅ R6 rdf+ontology run 3 graded by code

A-. A26 (AS, 2023-05-01) is the rating in force on 2026-01-01; A27 (DG BBB+) is dated 2026-04-15.

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

✅ R6 rdf+ontology run 4 graded by code

A-. Halden Bank is E10 (E17 shares its LEI), and A26 (A-, 2023-05-01) is the rating on 2026-01-01; A27 (DG) came on 2026-04-15.

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

✅ R6 rdf+ontology run 5 graded by code

A-. E10 was rated A- by A26 (2023-05-01), and the downgrade to BBB+ (A27) came on 2026-04-15. E17 is a RESEARCH duplicate of E10 and has no actions.

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

✅ R5 csv+ontology run 1 graded by code

A-. The Halden Bank rating of A- (A26, 2023-05-01) held until the 2026-04-15 downgrade (A27). The RESEARCH record E17 is the same LEI and is ignored.

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

✅ R5 csv+ontology run 2 graded by code

A-. A26 (AS, 2023-05-01) was the rating until A27 (DG to BBB+) on 2026-04-15. E10 and E17 are the same entity, and RATINGS holds the parent and country.

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

✅ R5 csv+ontology run 3 graded by code

A-. The latest action before 1 January 2026 is A26 (A-), since the downgrade to BBB+ (A27) is dated 2026-04-15.

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

✅ R5 csv+ontology run 4 graded by code

A-. Halden Bank's 2026 downgrade to BBB+ (A27) comes after 1 Jan 2026, so the rating then was the A- set in 2023 (A26).

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

✅ R5 csv+ontology run 5 graded by code

A-
E10 and E17 share an LEI, so they are one entity; the 2026 downgrade (A27) came after 1 January 2026, so the rating then was A- from A26.

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

✅ R4 csv+markdown run 1 graded by code

A-. A26 (2023-05-01) set A-, and E10's downgrade to BBB+ (A27) is dated 2026-04-15, after 2026-01-01. E17 is the same LEI as E10 and is merged.

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

✅ R4 csv+markdown run 2 graded by code

A-. E10 (Halden Bank AG) was A- until its downgrade to BBB+ on 2026-04-15 (A27). E17 is the same entity by LEI and has no rating actions.

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

✅ R4 csv+markdown run 3 graded by code

A-. E10 (also E17, same LEI) was rated A- by A26 (2023), and the downgrade to BBB+ (A27) came on 15 Apr 2026.

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

✅ R4 csv+markdown run 4 graded by code

A-. E10's rating was A- from A26 (2023-05-01) until the downgrade to BBB+ on 2026-04-15 (A27), which is after 1 Jan 2026.

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

✅ R4 csv+markdown run 5 graded by code

A-. A26 is the latest action on or before 1 Jan 2026; A27 (BBB+) came later, on 2026-04-15. The RESEARCH record E17 is the same LEI and has no rating actions.

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

✅ R3 csv+padding run 1 graded by code

A-. Halden Bank's rating was A- from 2023 (A26) until the 2026-04-15 downgrade to BBB+ (A27). E17 is the same LEI as E10 and has no rating actions.

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

✅ R3 csv+padding run 2 graded by code

A-. E10's A- (A26, 2023-05-01) stood until the downgrade to BBB+ in A27 (2026-04-15).

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

✅ R3 csv+padding run 3 graded by code

A-. A26 assigned A- and A27 (2026-04-15) cut it to BBB+, so A- was in place on 1 Jan 2026; E17 is a duplicate with no rating actions.

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

✅ R3 csv+padding run 4 graded by code

A-. A26 (2023) set A-, and the first later action, A27 (2026-04-15), moved it to BBB+, so the rating on 1 January 2026 was still A-.

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

✅ R3 csv+padding run 5 graded by code

A-. E10 (Halden Bank AG) was rated A- (A26), and its downgrade to BBB+ came on 2026-04-15 (A27). E17, the other "Halden Bank" record, has no ratings.

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