BIZTRAC BETA
Rental and operating of own or leased real estate

REPPEN EIENDOM AS

Org. no. 926129295 Limited company (AS) Narvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 598,000
Operating profit NOK 394,000
Equity NOK 4.2m
Incorporated 2020
Share capital NOK 60,000

REPPEN EIENDOM AS is registered as a limited company in Narvik, Nordland with organisation number 926129295. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Investering i og forvaltning av eiendommer, maskiner og utstyr for utleie og videresalg, samt å plassere overskuddslikviditet i bankinnskudd, aksjefond eller andre selskap med økonomisk aktivitet.”. The most recent filed accounts, for the 2024 financial year, show NOK 598,000 in revenue and NOK 394,000 in operating profit.

Key figures · 2024

Revenue
NOK 598,000
Operating profit
NOK 394,000
Equity
NOK 4.2m
Est. value
NOK 3.5m

Financial health · 2024

Liquidity
0.66
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.3%
Very good
Equity as a share of total capital

Who owns REPPEN EIENDOM AS?

RELOGRUPPEN AS
REPPEN EIENDOM AS
NOK 598,000 rev. · NOK 394,000 profit

REPPEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REPPEN EIENDOM AS

Who owns REPPEN EIENDOM AS?

RELOGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of REPPEN EIENDOM AS?

REPPEN EIENDOM AS had revenue of NOK 598,000 in 2024.

Who is the general manager of REPPEN EIENDOM AS?

Trygve Losvik Reppen is registered as general manager of REPPEN EIENDOM AS.

Where is REPPEN EIENDOM AS based?

REPPEN EIENDOM AS has its business address in Ankenes.

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.