BIZTRAC BETA
COMPANY REGISTER PROFILE
889030712 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

STRANDGATEN 60 NÆRINGSUTVIKLING AS

Org. no. 889030712 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 563,000
Operating profit NOK 501,000
Equity NOK 984,000
Incorporated 2005
Share capital NOK 500,000

STRANDGATEN 60 NÆRINGSUTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 889030712. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom og eiendomsdrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 563,000 in revenue and NOK 501,000 in operating profit.

Key figures · 2025

Revenue
NOK 563,000
▼ −1 %
Operating profit
NOK 501,000
▲ +47 %
Equity
NOK 984,000
▲ +1 %
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
31.8%
Very good
Return on total assets
Solidity
52.6%
Very good
Equity as a share of total capital

Who owns STRANDGATEN 60 NÆRINGSUTVIKLING AS?

STRANDGATEN 60 NÆRINGSUTVIKLING AS
NOK 563,000 rev. · NOK 501,000 profit

STRANDGATEN 60 NÆRINGSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDGATEN 60 NÆRINGSUTVIKLING AS

Who owns STRANDGATEN 60 NÆRINGSUTVIKLING AS?

AMAR PREET SINGH is the largest registered owner, with 100.0%.

What is the revenue of STRANDGATEN 60 NÆRINGSUTVIKLING AS?

STRANDGATEN 60 NÆRINGSUTVIKLING AS had revenue of NOK 563,000 in 2025.

Where is STRANDGATEN 60 NÆRINGSUTVIKLING AS based?

STRANDGATEN 60 NÆRINGSUTVIKLING 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 02.09.2026.

Report a problem

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