BIZTRAC BETA
Service activities incidental to water transportation

STRANDGATEN 35 AS

Org. no. 990894442 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 110,000
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STRANDGATEN 35 AS is registered as a limited company in Stavanger, Rogaland with organisation number 990894442. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Forsyningsbase-, havne- og agenttjenester, samt utvikling, investering, salg og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 110,000
Est. value
NOK 117,000

Financial health · 2025

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

Who owns STRANDGATEN 35 AS?

SEABROKERS EIENDOM AS
STRANDGATEN 35 AS
NOK 0 rev. · NOK −9,000 profit

STRANDGATEN 35 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDGATEN 35 AS

Who owns STRANDGATEN 35 AS?

SEABROKERS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of STRANDGATEN 35 AS?

STRANDGATEN 35 AS had revenue of NOK 0 in 2025.

Where is STRANDGATEN 35 AS based?

STRANDGATEN 35 AS has its business address in Stavanger.

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.