biztrac. BETA
COMPANY REGISTER PROFILE
927421275 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities auxiliary to insurance and pension funding n.e.c.

SIMEN ORMBERG HOLDING AS

Org. no. 927421275 Limited company (AS) Bergen Incorporated 2021 Active
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 39,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).

SIMEN ORMBERG HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 927421275. The business is classified under activities auxiliary to insurance and pension funding n.e.c. (NACE 66.290). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −1,000
▼ −122 %
Equity
NOK 39,000
▼ −3 %
Est. value
NOK 24,000

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
-2.9%
Not satisfactory
Return on total assets
Solidity
88.9%
Weak
Equity as a share of total capital

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

Who owns SIMEN ORMBERG HOLDING AS?

SIMEN ORMBERG HOLDING AS
NOK 0 rev. · NOK −1,000 profit

SIMEN ORMBERG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIMEN ORMBERG HOLDING AS

Who owns SIMEN ORMBERG HOLDING AS?

Simen Ormberg is the largest registered owner, with 100.0%.

What is the revenue of SIMEN ORMBERG HOLDING AS?

SIMEN ORMBERG HOLDING AS had revenue of NOK 0 in 2025.

Where is SIMEN ORMBERG HOLDING AS based?

SIMEN ORMBERG 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.