BIZTRAC BETA
Manufacture of plastic packing goods

ATLANTIC STYRO AS

Org. no. 913997085 Limited company (AS) Lurøy Incorporated 1978 Active
Ownership graph ↗
Revenue 2024 NOK 98.6m
Operating profit NOK 28.4m
Equity NOK 13.0m
Incorporated 1978
Employees 9
Share capital NOK 1.3m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ATLANTIC STYRO AS is registered as a limited company in Lurøy, Nordland with organisation number 913997085. The business is classified under manufacture of plastic packing goods (NACE 22.220). The company was incorporated in 1978 and has 9 registered employees. Registered share capital is NOK 1.3m, divided into 1316 shares. The company's stated purpose is: “Produsere og selge styroporprodukter og/eller beslektede produkter, samt drive annen næringsvirksomhet. Selskapet kan ved innskudd eller på annen måte gjøre seg intressert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 98.6m in revenue and NOK 28.4m in operating profit.

Key figures · 2024

Revenue
NOK 98.6m
Operating profit
NOK 28.4m
Equity
NOK 13.0m
Est. value
NOK 93.1m

Financial health · 2024

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

Who owns ATLANTIC STYRO AS?

BUR HOLDING AS
ATLANTIC STYRO AS
NOK 98.6m rev. · NOK 28.4m profit

ATLANTIC STYRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ATLANTIC STYRO AS

Who owns ATLANTIC STYRO AS?

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

What is the revenue of ATLANTIC STYRO AS?

ATLANTIC STYRO AS had revenue of NOK 98.6m in 2024.

Where is ATLANTIC STYRO AS based?

ATLANTIC STYRO AS has its business address in Lovund.

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.