biztrac. BETA
COMPANY REGISTER PROFILE
919009659 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

STRANDGATA 3 EIENDOM AS

Org. no. 919009659 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 219,000
Equity NOK 3.3m
Incorporated 2017
Share capital NOK 90,000

Signals

1 flags
  • Nylig endring 2026-08-27 Adresseendring registrert 2026-08-27.

STRANDGATA 3 EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 919009659. 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 90,000, divided into 30 shares. The company's stated purpose is: “Eie, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 219,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +209 %
Operating profit
NOK 219,000
▲ +436 %
Equity
NOK 3.3m
▼ −1 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
3.1%
Weak
Return on total assets
Solidity
48.9%
Very good
Equity as a share of total capital

Who owns STRANDGATA 3 EIENDOM AS?

STRANDGATA 3 EIENDOM AS
NOK 1.7m rev. · NOK 219,000 profit

STRANDGATA 3 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDGATA 3 EIENDOM AS

Who owns STRANDGATA 3 EIENDOM AS?

EKCS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STRANDGATA 3 EIENDOM AS?

STRANDGATA 3 EIENDOM AS had revenue of NOK 1.7m in 2025.

Where is STRANDGATA 3 EIENDOM AS based?

STRANDGATA 3 EIENDOM AS has its business address in Sandvika.

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.