biztrac. BETA
COMPANY REGISTER PROFILE
932848864 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Non-life insurance

ALANDIA FÖRSÄKRING ABP NUF

Org. no. 932848864 Norwegian division of foreign business enterprise (NUF) Oslo Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK −693,000
Equity NOK −444,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−444k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−693k kr).
  • Nylig endring 2026-09-15 Adresseendring registrert 2026-09-15.

ALANDIA FÖRSÄKRING ABP NUF is registered as a norwegian division of foreign business enterprise in Oslo, Oslo with organisation number 932848864. The business is classified under non-life insurance (NACE 65.120). The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −693,000 in operating profit.

Former names: ALANDIA NUF

Key figures · 2025

Revenue
NOK 1.6m
▼ −1 %
Operating profit
NOK −693,000
▼ −317 %
Equity
NOK −444,000
▼ −278 %

Financial health · 2025

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-39.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ALANDIA FÖRSÄKRING ABP NUF?

No shareholders are registered for ALANDIA FÖRSÄKRING ABP NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ALANDIA FÖRSÄKRING ABP NUF

What is the revenue of ALANDIA FÖRSÄKRING ABP NUF?

ALANDIA FÖRSÄKRING ABP NUF had revenue of NOK 1.6m in 2025.

Who is the general manager of ALANDIA FÖRSÄKRING ABP NUF?

Tony Albin Karlström is registered as general manager of ALANDIA FÖRSÄKRING ABP NUF.

Where is ALANDIA FÖRSÄKRING ABP NUF based?

ALANDIA FÖRSÄKRING ABP NUF has its business address in Oslo.

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

Report a problem

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