BIZTRAC BETA
Construction of residential and non-residential buildings

MELLEBYGG AS

Org. no. 988975699 Limited company (AS) Lørenskog Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 373,000
Operating profit NOK 53,000
Equity NOK 280,000
Incorporated 2005
Share capital NOK 30,000

MELLEBYGG AS is registered as a limited company in Lørenskog, Akershus with organisation number 988975699. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rehabilitering og oppføring av bygg samt investere i aksjer innen byggebransjen og deltagelse i andre virksomheter, samt yte finansiell bistand til selskap som eies direkte eller indirekte. Selskapet kan også yte konsulentbistand.”. The most recent filed accounts, for the 2025 financial year, show NOK 373,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2025

Revenue
NOK 373,000
Operating profit
NOK 53,000
Equity
NOK 280,000
Est. value
NOK 300,000

Financial health · 2025

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

Who owns MELLEBYGG AS?

FREDRIK MELLEBY
MELLEBYGG AS
NOK 373,000 rev. · NOK 53,000 profit

MELLEBYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MELLEBYGG AS own?

MELLEBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MELLEBYGG AS

Who owns MELLEBYGG AS?

FREDRIK MELLEBY is the largest registered owner, with 100.0%.

What is the revenue of MELLEBYGG AS?

MELLEBYGG AS had revenue of NOK 373,000 in 2025.

Where is MELLEBYGG AS based?

MELLEBYGG AS has its business address in Lørenskog.

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.