BIZTRAC BETA
Sound recording and music publishing activities

MHOST LIKELY AS

Org. no. 925898031 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 207,000
Operating profit NOK 34,000
Equity NOK 11,000
Incorporated 2020
Share capital NOK 30,000

MHOST LIKELY AS is registered as a limited company in Bergen, Vestland with organisation number 925898031. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å være et plateselskap, herunder produksjon av lyd og musikk, fysisk og digitale lydopptak, samt impresariovirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 207,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 207,000
Operating profit
NOK 34,000
Equity
NOK 11,000
Est. value
NOK 208,000

Financial health · 2025

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

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

Who owns MHOST LIKELY AS?

OLAV JOHANNES GREINER HALLANGER
MHOST LIKELY AS
NOK 207,000 rev. · NOK 34,000 profit

MHOST LIKELY AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MHOST LIKELY AS

Who owns MHOST LIKELY AS?

OLAV JOHANNES GREINER HALLANGER is the largest registered owner, with 33.4%.

What is the revenue of MHOST LIKELY AS?

MHOST LIKELY AS had revenue of NOK 207,000 in 2025.

Who is the general manager of MHOST LIKELY AS?

Magnus Kløvnes Lauritzen is registered as general manager of MHOST LIKELY AS.

Where is MHOST LIKELY AS based?

MHOST LIKELY AS has its business address in Bergen.

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.