BIZTRAC BETA
Other real estate activities on a fee or contract basis

SLETTESTRANDVEIEN 2 AS

Org. no. 887894892 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 2.4m
Equity NOK 7.0m
Incorporated 2005
Share capital NOK 500,000

Signals

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

SLETTESTRANDVEIEN 2 AS is registered as a limited company in Oslo, Oslo with organisation number 887894892. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 2.4m
Equity
NOK 7.0m
Est. value
NOK 9.5m

Financial health · 2024

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.8%
Very good
Equity as a share of total capital

Who owns SLETTESTRANDVEIEN 2 AS?

GAUSEL STASJON NÆRINGSPARK AS
SLETTESTRANDVEIEN 2 AS
NOK 2.8m rev. · NOK 2.4m profit

SLETTESTRANDVEIEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SLETTESTRANDVEIEN 2 AS

Who owns SLETTESTRANDVEIEN 2 AS?

GAUSEL STASJON NÆRINGSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of SLETTESTRANDVEIEN 2 AS?

SLETTESTRANDVEIEN 2 AS had revenue of NOK 2.8m in 2024.

Where is SLETTESTRANDVEIEN 2 AS based?

SLETTESTRANDVEIEN 2 AS has its business address in Oslo.

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.