BIZTRAC BETA
Rental and operating of own or leased real estate

RIISEKULEN EIGEDOM AS

Org. no. 932040999 Limited company (AS) Stryn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.6m
Equity NOK 1.1m
Incorporated 2023
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-06-04 Aksjekapital registrert 2026-06-04.

RIISEKULEN EIGEDOM AS is registered as a limited company in Stryn, Vestland with organisation number 932040999. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp/salg/utleige av fast eigedom. Oppussing og utvikling av eigedom. Investering i eigedom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.6m
Equity
NOK 1.1m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns RIISEKULEN EIGEDOM AS?

K.NESJE HOLDING AS
RIISEKULEN EIGEDOM AS
NOK 1.8m rev. · NOK 1.6m profit

RIISEKULEN EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RIISEKULEN EIGEDOM AS

Who owns RIISEKULEN EIGEDOM AS?

K.NESJE HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of RIISEKULEN EIGEDOM AS?

RIISEKULEN EIGEDOM AS had revenue of NOK 1.8m in 2025.

Who is the general manager of RIISEKULEN EIGEDOM AS?

Kristian Nesje is registered as general manager of RIISEKULEN EIGEDOM AS.

Where is RIISEKULEN EIGEDOM AS based?

RIISEKULEN EIGEDOM AS has its business address in Stryn.

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.