BIZTRAC BETA
Rental and operating of own or leased real estate

KAUPANGER EIGEDOMSSELSKAP AS

Org. no. 928290271 Limited company (AS) Sogndal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 1.0m
Equity NOK 3.9m
Incorporated 2021
Share capital NOK 36,000

Signals

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

KAUPANGER EIGEDOMSSELSKAP AS is registered as a limited company in Sogndal, Vestland with organisation number 928290271. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 36,000, divided into 200 shares. The company's stated purpose is: “Utvikling og utleie av fast eiendom, og alt som hermed står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 1.0m
Equity
NOK 3.9m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns KAUPANGER EIGEDOMSSELSKAP AS?

ANI ANLEGG AS
KAUPANGER EIGEDOMSSELSKAP AS
NOK 1.9m rev. · NOK 1.0m profit

KAUPANGER EIGEDOMSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAUPANGER EIGEDOMSSELSKAP AS

Who owns KAUPANGER EIGEDOMSSELSKAP AS?

ANI ANLEGG AS is the largest registered owner, with 100.0%.

What is the revenue of KAUPANGER EIGEDOMSSELSKAP AS?

KAUPANGER EIGEDOMSSELSKAP AS had revenue of NOK 1.9m in 2024.

Where is KAUPANGER EIGEDOMSSELSKAP AS based?

KAUPANGER EIGEDOMSSELSKAP AS has its business address in Kaupanger.

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.