BIZTRAC BETA
Buying and selling of own real estate

KVALVIK EIENDOM AS

Org. no. 918115439 Limited company (AS) Karmøy Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −25,000
Equity NOK −188,000
Incorporated 2016
Share capital NOK 300,000

Signals

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

KVALVIK EIENDOM AS is registered as a limited company in Karmøy, Rogaland with organisation number 918115439. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Investere og drive utleie av eiendom, samt hva hermed står i forbindelse, herunder å delta i andre foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK −188,000

Financial health · 2025

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

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

Who owns KVALVIK EIENDOM AS?

MAGNE JONNY JOHANNESEN
KVALVIK EIENDOM AS
NOK 0 rev. · NOK −25,000 profit

KVALVIK EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVALVIK EIENDOM AS

Who owns KVALVIK EIENDOM AS?

MAGNE JONNY JOHANNESEN is the largest registered owner, with 33.3%.

What is the revenue of KVALVIK EIENDOM AS?

KVALVIK EIENDOM AS had revenue of NOK 0 in 2025.

Where is KVALVIK EIENDOM AS based?

KVALVIK EIENDOM 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.