biztrac. BETA
COMPANY REGISTER PROFILE
926145215 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BUNDE MK AS

Org. no. 926145215 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 11.7m
Operating profit NOK 9.5m
Equity NOK −2.6m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,6 mill kr).

BUNDE MK AS is registered as a limited company in Oslo, Oslo with organisation number 926145215. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andre eierandeler i andre selskaper og foretak, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.7m in revenue and NOK 9.5m in operating profit.

Former names: BUNDE H9 AS

Key figures · 2025

Revenue
NOK 11.7m
▲ +117 %
Operating profit
NOK 9.5m
▲ +178 %
Equity
NOK −2.6m
▲ +59 %
Est. value
NOK 49.2m

Financial health · 2025

Liquidity
7.35
Very good
Current assets ÷ current liabilities
Profitability
15.4%
Very good
Return on total assets
Solidity
-10.3%
Weak
Equity as a share of total capital

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

Who owns BUNDE MK AS?

BUNDE MK AS
NOK 11.7m rev. · NOK 9.5m profit

BUNDE MK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUNDE MK AS

Who owns BUNDE MK AS?

BUNDE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BUNDE MK AS?

BUNDE MK AS had revenue of NOK 11.7m in 2025.

Where is BUNDE MK AS based?

BUNDE MK 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.