biztrac. BETA
COMPANY REGISTER PROFILE
912479692 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

MOORE BERGEN HOLDING AS

Org. no. 912479692 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −58,000
Equity NOK −27,000
Incorporated 2013
Share capital NOK 41,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−27k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−58k kr).

MOORE BERGEN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 912479692. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 41,000, divided into 41144 shares. The company's stated purpose is: “Finansiell tjenesteyting, rådgivning, investering i aksjer og andre eiendeler samt annen virksomhet som står i forbindelse.”.

Former names: SPITSBERGEN FORVALTNING AS

Key figures · 2025

Operating profit
NOK −58,000
▼ −85 %
Equity
NOK −27,000
▼ −108 %

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
-16.3%
Not satisfactory
Return on total assets
Solidity
-7.8%
Weak
Equity as a share of total capital

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

Who owns MOORE BERGEN HOLDING AS?

MOORE BERGEN HOLDING AS has 6 registered shareholders:

All shareholders and roles →

Which companies does MOORE BERGEN HOLDING AS own?

MOORE BERGEN HOLDING AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about MOORE BERGEN HOLDING AS

Who owns MOORE BERGEN HOLDING AS?

Jan Erik Pahr Alvheim is the largest registered owner, with 70.1%.

Where is MOORE BERGEN HOLDING AS based?

MOORE BERGEN HOLDING AS has its business address in Bergen.

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.