BIZTRAC BETA
COMPANY REGISTER PROFILE
936583288 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

EIR BOREALIS AS

Org. no. 936583288 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-11-05.
  • Nylig endring 2026-09-01 Adresseendring registrert 2026-09-01.

EIR BOREALIS AS is registered as a limited company in Oslo, Oslo with organisation number 936583288. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eie og forvalte kapital, herunder eie og leie ut egen eiendom, og annet som faller naturlig sammen med dette - inkludert å eie unoterte og noterte verdipapirer eller derivater på disse.”.

Former names: JNHS 256 AS

Who owns EIR BOREALIS AS?

EIR BOREALIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIR BOREALIS AS

Who owns EIR BOREALIS AS?

JØRN LEIN-MATHISEN is the largest registered owner, with 100.0%.

Who is the general manager of EIR BOREALIS AS?

Jørn Lein-Mathisen is registered as general manager of EIR BOREALIS AS.

Where is EIR BOREALIS AS based?

EIR BOREALIS AS has its business address in Oslo.

Property

Business address c/o Jørn Lein-Mathisen Olav Kyrres gate 10, 0273 Oslo
Cadastral unit 301-212/735/0/0
Building Andre småhus med 3 boliger eller flere · 3 units

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.