biztrac. BETA
COMPANY REGISTER PROFILE
815261232 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

GARVIK-GRUPPEN AS

Org. no. 815261232 Limited company (AS) Karmøy Incorporated 2015 Active
Operating profit NOK −169,000
Equity NOK 8.3m
Incorporated 2015
Share capital NOK 60,000

Signals

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

GARVIK-GRUPPEN AS is registered as a limited company in Karmøy, Rogaland with organisation number 815261232. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, samt det som naturlig står i forbindelse med dette”.

Key figures · 2025

Operating profit
NOK −169,000
▼ −16 %
Equity
NOK 8.3m
▲ +166 %
Est. value
NOK 100.9m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
64.2%
Very good
Return on total assets
Solidity
24.7%
Good
Equity as a share of total capital

Who owns GARVIK-GRUPPEN AS?

GARVIK-GRUPPEN AS
· NOK −169,000 profit

GARVIK-GRUPPEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does GARVIK-GRUPPEN AS own?

GARVIK-GRUPPEN AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

GARVIK-GRUPPEN AS er morselskap for 3 datterselskaper:

Frequently asked questions about GARVIK-GRUPPEN AS

Who owns GARVIK-GRUPPEN AS?

BGG HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of GARVIK-GRUPPEN AS?

Gabriel Reidar Garvik is registered as general manager of GARVIK-GRUPPEN AS.

Where is GARVIK-GRUPPEN AS based?

GARVIK-GRUPPEN AS has its business address in Kopervik.

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.