BIZTRAC BETA
Construction of utility projects for fluids

SVK AS

Org. no. 992627271 Limited company (AS) Stavanger Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 52,000
Operating profit NOK −43,000
Equity NOK 1.3m
Incorporated 2008
Share capital NOK 720,000

Signals

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

SVK AS is registered as a limited company in Stavanger, Rogaland with organisation number 992627271. The business is classified under construction of utility projects for fluids (NACE 42.210). The company was incorporated in 2008. Registered share capital is NOK 720,000, divided into 36 shares. The company's stated purpose is: “Bygge ut vann og avløpsnett til og innenfor Stølstjønn hytteområde ved Sinnes i Sirdal kommune. Virksomheten skal videre bestå i å selge vann og avløpstjenester til eksisterende og nye hytteeiere og til fremtidig servicevirksomhet som etableres i tilknytning til turisme i området, samt deltakelse av enhver art i andre virksomheter og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 52,000 in revenue and NOK −43,000 in operating profit.

Key figures · 2025

Revenue
NOK 52,000
Operating profit
NOK −43,000
Equity
NOK 1.3m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns SVK AS?

FINN GABRIELSEN
SVK AS
NOK 52,000 rev. · NOK −43,000 profit

SVK AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about SVK AS

Who owns SVK AS?

FINN GABRIELSEN is the largest registered owner, with 2.8%.

What is the revenue of SVK AS?

SVK AS had revenue of NOK 52,000 in 2025.

Where is SVK AS based?

SVK 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.