BIZTRAC BETA
Rental and operating of own or leased real estate

SILURVEIEN 1-9 AS

Org. no. 934653963 Limited company (AS) Kristiansand Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 711,000
Equity NOK 11.0m
Incorporated 2024
Share capital NOK 235,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SILURVEIEN 1-9 AS is registered as a limited company in Kristiansand, Agder with organisation number 934653963. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 235,000, divided into 47095 shares. The company's stated purpose is: “Utvikling, utbygging, kjøp, salg og utleie av eiendom, samt drift av fast eiendom og alt som herved står i forbindelse, herunder å delta i selskaper med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 711,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 711,000
Equity
NOK 11.0m
Est. value
NOK 8.7m

Financial health · 2024

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

Who owns SILURVEIEN 1-9 AS?

GUVI INVEST AS
SILURVEIEN 1-9 AS
NOK 2.0m rev. · NOK 711,000 profit

SILURVEIEN 1-9 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SILURVEIEN 1-9 AS

Who owns SILURVEIEN 1-9 AS?

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

What is the revenue of SILURVEIEN 1-9 AS?

SILURVEIEN 1-9 AS had revenue of NOK 2.0m in 2024.

Where is SILURVEIEN 1-9 AS based?

SILURVEIEN 1-9 AS has its business address in Kristiansand S.

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.