BIZTRAC BETA
Retail sale of other new goods

CHAINZ LIMITED AS

Org. no. 931471368 Limited company (AS) Lillehammer Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 15,000
Equity NOK 80,000
Incorporated 2023
Share capital NOK 30,000

CHAINZ LIMITED AS is registered as a limited company in Lillehammer, Innlandet with organisation number 931471368. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og produksjon av, smykker, armlenker og halsbånd via netthandel og fysiske utsalgssteder samt andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 15,000
Equity
NOK 80,000
Est. value
NOK 89,000

Financial health · 2024

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns CHAINZ LIMITED AS?

DANIELA BRUUN DE NEERGAARD
CHAINZ LIMITED AS
NOK 1.4m rev. · NOK 15,000 profit

CHAINZ LIMITED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHAINZ LIMITED AS

Who owns CHAINZ LIMITED AS?

DANIELA BRUUN DE NEERGAARD is the largest registered owner, with 100.0%.

What is the revenue of CHAINZ LIMITED AS?

CHAINZ LIMITED AS had revenue of NOK 1.4m in 2024.

Who is the general manager of CHAINZ LIMITED AS?

Oskar Nybråten is registered as general manager of CHAINZ LIMITED AS.

Where is CHAINZ LIMITED AS based?

CHAINZ LIMITED AS has its business address in Lillehammer.

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.