BIZTRAC BETA
Development of building projects

GROV SJØ AS

Org. no. 912804968 Limited company (AS) Stord Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK −143,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−143k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

GROV SJØ AS is registered as a limited company in Stord, Vestland with organisation number 912804968. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering, eiendomsutvikling, utleie av fast eiendom, utleie av båtplasser, kjøp og salg av eiendom, handel og hva dermed naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −143,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GROV SJØ AS?

SLITEVIK INVEST AS
GROV SJØ AS
NOK 0 rev. · NOK −12,000 profit

GROV SJØ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GROV SJØ AS

Who owns GROV SJØ AS?

SLITEVIK INVEST AS is the largest registered owner, with 33.3%.

What is the revenue of GROV SJØ AS?

GROV SJØ AS had revenue of NOK 0 in 2025.

Who is the general manager of GROV SJØ AS?

Kjell Jr Framnes is registered as general manager of GROV SJØ AS.

Where is GROV SJØ AS based?

GROV SJØ AS has its business address in Stord.

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.