BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

MØYLAND DRIFT AS

Org. no. 934416260 Limited company (AS) Sandefjord Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 576,000
Equity NOK 478,000
Incorporated 2024
Share capital NOK 50,000

MØYLAND DRIFT AS is registered as a limited company in Sandefjord, Vestfold with organisation number 934416260. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Gårdsutsalg / gårdsbutikk, vedsalg og entreprenørtjenester som brøyting og graving. Dessuten aktiviteter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 576,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 576,000
Equity
NOK 478,000
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns MØYLAND DRIFT AS?

SYNNØVE ASKE MØYLAND
MØYLAND DRIFT AS
NOK 3.3m rev. · NOK 576,000 profit

MØYLAND DRIFT AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MØYLAND DRIFT AS

Who owns MØYLAND DRIFT AS?

SYNNØVE ASKE MØYLAND is the largest registered owner, with 40.0%.

What is the revenue of MØYLAND DRIFT AS?

MØYLAND DRIFT AS had revenue of NOK 3.3m in 2025.

Where is MØYLAND DRIFT AS based?

MØYLAND DRIFT AS has its business address in Andebu.

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.