BIZTRAC BETA
Buying and selling of own real estate

RANDOR EIENDOM AS

Org. no. 982325455 Limited company (AS) Hamar Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 368,000
Operating profit NOK 213,000
Equity NOK 1.9m
Incorporated 2000
Share capital NOK 32,000

RANDOR EIENDOM AS is registered as a limited company in Hamar, Innlandet with organisation number 982325455. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2000. Registered share capital is NOK 32,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, leie og utleie av eiendommer av enhver art samt utvikling av egne eller andres eiendommer. I tillegg kan selskapet delta i andre selskap av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 368,000 in revenue and NOK 213,000 in operating profit.

Key figures · 2024

Revenue
NOK 368,000
Operating profit
NOK 213,000
Equity
NOK 1.9m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.5%
Good
Equity as a share of total capital

Who owns RANDOR EIENDOM AS?

RANDOR AS
RANDOR EIENDOM AS
NOK 368,000 rev. · NOK 213,000 profit

RANDOR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RANDOR EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about RANDOR EIENDOM AS

Who owns RANDOR EIENDOM AS?

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

What is the revenue of RANDOR EIENDOM AS?

RANDOR EIENDOM AS had revenue of NOK 368,000 in 2024.

Who is the general manager of RANDOR EIENDOM AS?

Kjetil Melleby is registered as general manager of RANDOR EIENDOM AS.

Where is RANDOR EIENDOM AS based?

RANDOR EIENDOM AS has its business address in Hamar.

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.