BIZTRAC BETA
Business and other management consultancy activities

MERKABAPHI AS

Org. no. 919920432 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 29,000
Operating profit NOK −297,000
Equity NOK 209,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

MERKABAPHI AS is registered as a limited company in Oslo, Oslo with organisation number 919920432. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap. Investering i aksjer og øvrige verdipapirer. Konsulenttjenester relatert til ledelse, administrasjon og bedriftsutvikling.”. The most recent filed accounts, for the 2024 financial year, show NOK 29,000 in revenue and NOK −297,000 in operating profit.

Key figures · 2024

Revenue
NOK 29,000
Operating profit
NOK −297,000
Equity
NOK 209,000
Est. value
NOK 131,000

Financial health · 2025

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

Who owns MERKABAPHI AS?

THOMAS FRANCIS ANGLERO
MERKABAPHI AS
NOK 29,000 rev. · NOK −297,000 profit

MERKABAPHI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MERKABAPHI AS own?

MERKABAPHI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MERKABAPHI AS

Who owns MERKABAPHI AS?

THOMAS FRANCIS ANGLERO is the largest registered owner, with 100.0%.

What is the revenue of MERKABAPHI AS?

MERKABAPHI AS had revenue of NOK 29,000 in 2024.

Where is MERKABAPHI AS based?

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