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

SYRR EIGEDOM INVEST AS

Org. no. 979191782 Limited company (AS) Sandefjord Incorporated 1997 Active
Revenue 2025 NOK 28,000
Operating profit NOK −225,000
Equity NOK 217,000
Incorporated 1997
Share capital NOK 1.4m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−225k kr).

SYRR EIGEDOM INVEST AS is registered as a limited company in Sandefjord, Vestfold with organisation number 979191782. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 1.4m, divided into 280 shares. The company's stated purpose is: “Kjøp, sal og utleige av eigedom og det som høyrer inn under dette i Norge. Selskapet kan og delta som aksjonær, eller på anna måte ved investering i andre verksemder.”. The most recent filed accounts, for the 2025 financial year, show NOK 28,000 in revenue and NOK −225,000 in operating profit.

Key figures · 2025

Revenue
NOK 28,000
▼ −65 %
Operating profit
NOK −225,000
▼ −8 %
Equity
NOK 217,000
▼ −46 %

Financial health · 2025

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

Who owns SYRR EIGEDOM INVEST AS?

SYRR EIGEDOM INVEST AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYRR EIGEDOM INVEST AS

Who owns SYRR EIGEDOM INVEST AS?

Rune Vikersveen is the largest registered owner, with 77.5%.

What is the revenue of SYRR EIGEDOM INVEST AS?

SYRR EIGEDOM INVEST AS had revenue of NOK 28,000 in 2025.

Where is SYRR EIGEDOM INVEST AS based?

SYRR EIGEDOM INVEST AS has its business address in Sandefjord.

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.