BIZTRAC BETA
COMPANY REGISTER PROFILE
928876500 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

MARHEMA AS

Org. no. 928876500 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Equity NOK −104,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−104k kr).

MARHEMA AS is registered as a limited company in Oslo, Oslo with organisation number 928876500. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Eie og forvalte aksjer, verdipapirer og andre formuesgjenstander av hvilken som helst art.”.

Key figures · 2025

Equity
NOK −104,000
▼ −127 %

Financial health · 2025

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

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

Who owns MARHEMA AS?

MARHEMA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MARHEMA AS own?

MARHEMA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MARHEMA AS

Who owns MARHEMA AS?

KRISTIAN ROSANDER HAFSTEEN is the largest registered owner, with 100.0%.

Where is MARHEMA AS based?

MARHEMA AS has its business address in Oslo.

Property

Business address Krags vei 12, 0783 Oslo
Cadastral unit 301-33/406/0/0
Building Enebolig · 1 unit

2 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.