BIZTRAC BETA
Construction of residential and non-residential buildings

MF BYGG AS

Org. no. 918788891 Limited company (AS) Lillestrøm Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 189,000
Equity NOK −95,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−95k kr).

MF BYGG AS is registered as a limited company in Lillestrøm, Akershus with organisation number 918788891. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tømrervirksomhet og kjøp/salg av bygningsmaterialer, samt kjøp/salg av aksjer og alt som naturlig faller herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 189,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 189,000
Equity
NOK −95,000
Est. value
NOK 1.3m

Financial health · 2025

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

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

Who owns MF BYGG AS?

MARIUS KAMP HELGESEN
MF BYGG AS
NOK 4.6m rev. · NOK 189,000 profit

MF BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MF BYGG AS

Who owns MF BYGG AS?

MARIUS KAMP HELGESEN is the largest registered owner, with 50.0%.

What is the revenue of MF BYGG AS?

MF BYGG AS had revenue of NOK 4.6m in 2025.

Who is the general manager of MF BYGG AS?

Fredrik Enger Holmberg is registered as general manager of MF BYGG AS.

Where is MF BYGG AS based?

MF BYGG AS has its business address in Skjetten.

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.