BIZTRAC BETA
Rental and operating of own or leased real estate

KVAMNET EIGEDOM AS

Org. no. 982710316 Limited company (AS) Kvam Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 830,000
Equity NOK 1.2m
Incorporated 2000
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KVAMNET EIGEDOM AS is registered as a limited company in Kvam, Vestland with organisation number 982710316. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utvikling og omsetning av eiendommer og beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 830,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 830,000
Equity
NOK 1.2m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns KVAMNET EIGEDOM AS?

KVAMNET HOLDING AS
KVAMNET EIGEDOM AS
NOK 1.5m rev. · NOK 830,000 profit

KVAMNET EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVAMNET EIGEDOM AS

Who owns KVAMNET EIGEDOM AS?

KVAMNET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KVAMNET EIGEDOM AS?

KVAMNET EIGEDOM AS had revenue of NOK 1.5m in 2024.

Who is the general manager of KVAMNET EIGEDOM AS?

Steinar Foss Andersen is registered as general manager of KVAMNET EIGEDOM AS.

Where is KVAMNET EIGEDOM AS based?

KVAMNET EIGEDOM AS has its business address in Norheimsund.

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.