biztrac. BETA
COMPANY REGISTER PROFILE
915631665 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SJØMANNSVEIEN 1 TOMTESELSKAP AS

Org. no. 915631665 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 20,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

SJØMANNSVEIEN 1 TOMTESELSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 915631665. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Handel-, investering- og eiendomsvirksomhet, samt å delta i andre selskaper med slik virksomhet.”.

Former names: SJØMANNSVEIEN 1 TOMT AS

Key figures · 2025

Operating profit
NOK −7,000
▼ −5 %
Equity
NOK 20,000
▼ −25 %
Est. value
NOK 18,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SJØMANNSVEIEN 1 TOMTESELSKAP AS?

SJØMANNSVEIEN 1 TOMTESELSKAP AS
· NOK −7,000 profit

SJØMANNSVEIEN 1 TOMTESELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SJØMANNSVEIEN 1 TOMTESELSKAP AS

Who owns SJØMANNSVEIEN 1 TOMTESELSKAP AS?

FREDENSBORG AS is the largest registered owner, with 100.0%.

Where is SJØMANNSVEIEN 1 TOMTESELSKAP AS based?

SJØMANNSVEIEN 1 TOMTESELSKAP 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.