BIZTRAC BETA
Rental and operating of own or leased real estate

SLETTAVEIEN 18 AS

Org. no. 918781854 Limited company (AS) Vestby Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 461,000
Equity NOK 2.4m
Incorporated 2017
Share capital NOK 2.3m

Signals

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

SLETTAVEIEN 18 AS is registered as a limited company in Vestby, Akershus with organisation number 918781854. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 2.3m, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg samt utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 461,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 461,000
Equity
NOK 2.4m
Est. value
NOK 2.3m

Financial health · 2024

Liquidity
3.11
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.8%
Satisfactory
Equity as a share of total capital

Who owns SLETTAVEIEN 18 AS?

BRØDRENE THOMASSEN EIENDOM AS
SLETTAVEIEN 18 AS
NOK 1.3m rev. · NOK 461,000 profit

SLETTAVEIEN 18 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLETTAVEIEN 18 AS

Who owns SLETTAVEIEN 18 AS?

BRØDRENE THOMASSEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SLETTAVEIEN 18 AS?

SLETTAVEIEN 18 AS had revenue of NOK 1.3m in 2024.

Who is the general manager of SLETTAVEIEN 18 AS?

Monica Siv Thomassen is registered as general manager of SLETTAVEIEN 18 AS.

Where is SLETTAVEIEN 18 AS based?

SLETTAVEIEN 18 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.