biztrac. BETA
COMPANY REGISTER PROFILE
870890192 ORG. NO. 2025 ACCOUNTS 12 SECTIONS
Active UPDATED 03.10.2026
Manufacture of builders’ ware of plastic

OLDROYD AS

Org. no. 870890192 Limited company (AS) Bamble Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 93.0m
Operating profit NOK 9.1m
Equity NOK 34.3m
Incorporated 1994
Employees 26
Share capital NOK 315,000

OLDROYD AS is registered as a limited company in Bamble, Telemark with organisation number 870890192. The business is classified under manufacture of builders’ ware of plastic (NACE 22.240). The company was incorporated in 1994 and has 26 registered employees. Registered share capital is NOK 315,000, divided into 315277 shares. The company's stated purpose is: “Drive virksomhet innen produksjon av plastprodukter og byggemateriell.”. The most recent filed accounts, for the 2025 financial year, show NOK 93.0m in revenue and NOK 9.1m in operating profit.

Former names: OLDROYD SYSTEMER AS

Key figures · 2025

Revenue
NOK 93.0m
▼ −3 %
Operating profit
NOK 9.1m
▼ −14 %
Equity
NOK 34.3m
▲ +10 %
Est. value
NOK 46.4m

Financial health · 2025

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
11.9%
Good
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns OLDROYD AS?

OLDROYD AS
NOK 93.0m rev. · NOK 9.1m profit

OLDROYD AS has 2 registered shareholders:

All shareholders and roles →

Group structure

OLDROYD AS er morselskap for 1 datterselskap:

Frequently asked questions about OLDROYD AS

Who owns OLDROYD AS?

OLDROYD PRODUCTION AS is the largest registered owner, with 97.5%.

What is the revenue of OLDROYD AS?

OLDROYD AS had revenue of NOK 93.0m in 2025.

Who is the general manager of OLDROYD AS?

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

Where is OLDROYD AS based?

OLDROYD 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.