BIZTRAC BETA
Site preparation

MELLEBY DRIFT AS

Org. no. 929756800 Limited company (AS) Indre Østfold Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK 1.4m
Equity NOK 1.9m
Incorporated 2022
Employees 6
Share capital NOK 30,000

MELLEBY DRIFT AS is registered as a limited company in Indre Østfold, Østfold with organisation number 929756800. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Alt innen vei og anleggsdrift, herunder snøbrøyting, gatefeiing, samt det som faller naturlig i tilknytning til dette. I tillegg utleie av maskiner og arbeidskraft, investere i og utleie av fast eiendom. Utover dette eie og forvalte andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK 1.4m
Equity
NOK 1.9m
Est. value
NOK 4.8m

Financial health · 2024

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.5%
Good
Equity as a share of total capital

Who owns MELLEBY DRIFT AS?

JENS MARKESTAD
MELLEBY DRIFT AS
NOK 8.4m rev. · NOK 1.4m profit

MELLEBY DRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MELLEBY DRIFT AS

Who owns MELLEBY DRIFT AS?

JENS MARKESTAD is the largest registered owner, with 50.0%.

What is the revenue of MELLEBY DRIFT AS?

MELLEBY DRIFT AS had revenue of NOK 8.4m in 2024.

Who is the general manager of MELLEBY DRIFT AS?

Jens Markestad is registered as general manager of MELLEBY DRIFT AS.

Where is MELLEBY DRIFT AS based?

MELLEBY DRIFT AS has its business address in Båstad.

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.