BIZTRAC BETA
Manufacture of wooden containers

LOOPING AS

Org. no. 818644922 Limited company (AS) Lørenskog Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK −4.3m
Equity NOK 14.2m
Incorporated 2017
Employees 12
Share capital NOK 394,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,3 mill kr).

LOOPING AS is registered as a limited company in Lørenskog, Akershus with organisation number 818644922. The business is classified under manufacture of wooden containers (NACE 16.240). The company was incorporated in 2017 and has 12 registered employees. Registered share capital is NOK 394,000, divided into 393600 shares. The company's stated purpose is: “Utvikling, produksjon, salg, utleie og vedlikehold av gjenbruksemballasje.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK −4.3m in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK −4.3m
Equity
NOK 14.2m
Est. value
NOK 12.0m

Financial health · 2024

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.5%
Very good
Equity as a share of total capital

Who owns LOOPING AS?

STRØMSTANGEN AS
LOOPING AS
NOK 8.4m rev. · NOK −4.3m profit

LOOPING AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does LOOPING AS own?

LOOPING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOOPING AS

Who owns LOOPING AS?

STRØMSTANGEN AS is the largest registered owner, with 27.5%.

What is the revenue of LOOPING AS?

LOOPING AS had revenue of NOK 8.4m in 2024.

Who is the general manager of LOOPING AS?

Jens-Kristian Brustad is registered as general manager of LOOPING AS.

Where is LOOPING AS based?

LOOPING AS has its business address in Lørenskog.

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.