BIZTRAC BETA
Construction of residential and non-residential buildings

SVEGRO AS

Org. no. 992455241 Limited company (AS) Gjesdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 561,000
Operating profit NOK −129,000
Equity NOK 464,000
Incorporated 2008
Share capital NOK 100,000

Signals

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

SVEGRO AS is registered as a limited company in Gjesdal, Rogaland with organisation number 992455241. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Snekker-, tømrer- og annen håndverksvirksomhet og alt hva som står i naturlig forbindelse med dette, herunder deltagelse i andre selskap med samme eller tilknyttet formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 561,000 in revenue and NOK −129,000 in operating profit.

Key figures · 2025

Revenue
NOK 561,000
Operating profit
NOK −129,000
Equity
NOK 464,000
Est. value
NOK 395,000

Financial health · 2025

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

Who owns SVEGRO AS?

GRO KAASEN
SVEGRO AS
NOK 561,000 rev. · NOK −129,000 profit

SVEGRO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVEGRO AS

Who owns SVEGRO AS?

GRO KAASEN is the largest registered owner, with 65.0%.

What is the revenue of SVEGRO AS?

SVEGRO AS had revenue of NOK 561,000 in 2025.

Who is the general manager of SVEGRO AS?

Sverre Kaasen is registered as general manager of SVEGRO AS.

Where is SVEGRO AS based?

SVEGRO AS has its business address in Ålgård.

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.