BIZTRAC BETA
Development of building projects

MER BOLIG AS

Org. no. 913681215 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 353,000
Operating profit NOK 293,000
Equity NOK 815,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-16 Adresseendring registrert 2026-02-16.

MER BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 913681215. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapets virksomhet er konsulenttjenester, utvikling, kjøp og salg av eiendom, selskaper, aksjer og andre finansielle instrumenter, samt annen virksomhet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 353,000 in revenue and NOK 293,000 in operating profit.

Key figures · 2024

Revenue
NOK 353,000
Operating profit
NOK 293,000
Equity
NOK 815,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.2%
Very good
Equity as a share of total capital

Who owns MER BOLIG AS?

MARIUS NIELSEN MATATULA
MER BOLIG AS
NOK 353,000 rev. · NOK 293,000 profit

MER BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MER BOLIG AS own?

MER BOLIG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MER BOLIG AS

Who owns MER BOLIG AS?

MARIUS NIELSEN MATATULA is the largest registered owner, with 100.0%.

What is the revenue of MER BOLIG AS?

MER BOLIG AS had revenue of NOK 353,000 in 2024.

Where is MER BOLIG AS based?

MER BOLIG 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.