BIZTRAC BETA
Rental and operating of own or leased real estate

OLDROYD EIENDOM AS

Org. no. 920604005 Limited company (AS) Bamble Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 3.1m
Equity NOK 16.2m
Incorporated 2018
Share capital NOK 30,000

OLDROYD EIENDOM AS is registered as a limited company in Bamble, Telemark with organisation number 920604005. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å eie og tilrettelegge og leie ut lokaler til næringsformål, samt annen virksomhet som naturlig hører til dette, herunder deltakelse i andre foretagende ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 3.1m
Equity
NOK 16.2m
Est. value
NOK 15.2m

Financial health · 2024

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

Who owns OLDROYD EIENDOM AS?

OLDROYD HOLDING AS
OLDROYD EIENDOM AS
NOK 4.8m rev. · NOK 3.1m profit

OLDROYD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLDROYD EIENDOM AS

Who owns OLDROYD EIENDOM AS?

OLDROYD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OLDROYD EIENDOM AS?

OLDROYD EIENDOM AS had revenue of NOK 4.8m in 2024.

Who is the general manager of OLDROYD EIENDOM AS?

Linda Amanda Celin is registered as general manager of OLDROYD EIENDOM AS.

Where is OLDROYD EIENDOM AS based?

OLDROYD EIENDOM AS has its business address in Stathelle.

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.