biztrac. BETA
COMPANY REGISTER PROFILE
934623061 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

MEBERG HOLDING AS

Org. no. 934623061 Limited company (AS) Oslo Incorporated 2024 Active
Operating profit NOK −22,000
Equity NOK 2,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

MEBERG HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 934623061. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −22,000
Equity
NOK 2,000
▼ −92 %
Est. value
NOK 2,000

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.0%
Weak
Equity as a share of total capital

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

Who owns MEBERG HOLDING AS?

MEBERG HOLDING AS
· NOK −22,000 profit

MEBERG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEBERG HOLDING AS own?

MEBERG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MEBERG HOLDING AS

Who owns MEBERG HOLDING AS?

Olav Røed Meberg is the largest registered owner, with 100.0%.

Who is the general manager of MEBERG HOLDING AS?

Olav Røed Meberg is registered as general manager of MEBERG HOLDING AS.

Where is MEBERG HOLDING AS based?

MEBERG HOLDING AS 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.