BIZTRAC BETA
Computer consultancy and computer facilities management activities

M4P HOSTING AS

Org. no. 933189759 Limited company (AS) Nes Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 777,000
Operating profit NOK 15,000
Equity NOK 13,000
Incorporated 2024
Share capital NOK 30,000

M4P HOSTING AS is registered as a limited company in Nes, Akershus with organisation number 933189759. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 777,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 777,000
Operating profit
NOK 15,000
Equity
NOK 13,000
Est. value
NOK 73,000

Financial health · 2024

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

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

Who owns M4P HOSTING AS?

M4P HOLDING AS
M4P HOSTING AS
NOK 777,000 rev. · NOK 15,000 profit

M4P HOSTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about M4P HOSTING AS

Who owns M4P HOSTING AS?

M4P HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of M4P HOSTING AS?

M4P HOSTING AS had revenue of NOK 777,000 in 2024.

Who is the general manager of M4P HOSTING AS?

Johnny Moratti-Bergstrøm is registered as general manager of M4P HOSTING AS.

Where is M4P HOSTING AS based?

M4P HOSTING AS has its business address in Auli.

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.