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

SLETTA DRIFT EIENDOM AS

Org. no. 994419137 Limited company (AS) Vestby Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 1.9m
Equity NOK 1.0m
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SLETTA DRIFT EIENDOM AS is registered as a limited company in Vestby, Akershus with organisation number 994419137. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Selv eller gjennom deltakelse i andre virksomheter å kjøpe, selge, eie, utvikle og leie ut fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 1.9m
Equity
NOK 1.0m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns SLETTA DRIFT EIENDOM AS?

SON HOLDING AS
SLETTA DRIFT EIENDOM AS
NOK 3.1m rev. · NOK 1.9m profit

SLETTA DRIFT EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLETTA DRIFT EIENDOM AS

Who owns SLETTA DRIFT EIENDOM AS?

SON HOLDING AS is the largest registered owner, with 65.0%.

What is the revenue of SLETTA DRIFT EIENDOM AS?

SLETTA DRIFT EIENDOM AS had revenue of NOK 3.1m in 2025.

Where is SLETTA DRIFT EIENDOM AS based?

SLETTA DRIFT EIENDOM AS has its business address in Son.

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.