biztrac. BETA
COMPANY REGISTER PROFILE
887894892 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
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 2025 NOK 1.9m
Operating profit NOK 938,000
Equity NOK 7.0m
Incorporated 2005
Share capital NOK 500,000

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 2025 financial year, show NOK 1.9m in revenue and NOK 938,000 in operating profit.

Former names: SETTER EIENDOM AS

Key figures · 2025

Revenue
NOK 1.9m
▼ −32 %
Operating profit
NOK 938,000
▼ −61 %
Equity
NOK 7.0m
▼ −1 %
Est. value
NOK 7.0m

Financial health · 2025

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
6.9%
Satisfactory
Return on total assets
Solidity
44.6%
Very good
Equity as a share of total capital

Who owns SLETTESTRANDVEIEN 2 AS?

SLETTESTRANDVEIEN 2 AS
NOK 1.9m rev. · NOK 938,000 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 1.9m in 2025.

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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.