BIZTRAC BETA
Rental and operating of own or leased real estate

RADIN EIENDOM AS

Org. no. 925637769 Limited company (AS) Fredrikstad Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 63.7m
Operating profit NOK 4.4m
Equity NOK 15.5m
Incorporated 2020
Share capital NOK 4.4m

RADIN EIENDOM AS is registered as a limited company in Fredrikstad, Østfold with organisation number 925637769. 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 4.4m, divided into 4428 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom. Håndverkstjenester vil også kunne være aktuelt.”. The most recent filed accounts, for the 2024 financial year, show NOK 63.7m in revenue and NOK 4.4m in operating profit.

Key figures · 2024

Revenue
NOK 63.7m
Operating profit
NOK 4.4m
Equity
NOK 15.5m
Est. value
NOK 20.4m

Financial health · 2024

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.5%
Good
Equity as a share of total capital

Who owns RADIN EIENDOM AS?

AH CAPITAL AS
RADIN EIENDOM AS
NOK 63.7m rev. · NOK 4.4m profit

RADIN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does RADIN EIENDOM AS own?

RADIN EIENDOM AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about RADIN EIENDOM AS

Who owns RADIN EIENDOM AS?

AH CAPITAL AS is the largest registered owner, with 35.0%.

What is the revenue of RADIN EIENDOM AS?

RADIN EIENDOM AS had revenue of NOK 63.7m in 2024.

Who is the general manager of RADIN EIENDOM AS?

Amund Tvete Hermansen is registered as general manager of RADIN EIENDOM AS.

Where is RADIN EIENDOM AS based?

RADIN EIENDOM AS has its business address in Fredrikstad.

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.