BIZTRAC BETA
Retail sale of sports equipment

NIA LAPANSI AS

Org. no. 923783717 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 94,000
Operating profit NOK −77,000
Equity NOK −701,000
Incorporated 2019
Share capital NOK 130,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−701k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−77k kr).

NIA LAPANSI AS is registered as a limited company in Bærum, Akershus with organisation number 923783717. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2019. Registered share capital is NOK 130,000, divided into 130000 shares. The company's stated purpose is: “Produksjon og salg av yogautstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 94,000 in revenue and NOK −77,000 in operating profit.

Key figures · 2025

Revenue
NOK 94,000
Operating profit
NOK −77,000
Equity
NOK −701,000

Financial health · 2025

Liquidity
15.50
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-188.0%
Weak
Equity as a share of total capital

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

Who owns NIA LAPANSI AS?

Kamilla Schultz Seljelid
NIA LAPANSI AS
NOK 94,000 rev. · NOK −77,000 profit

NIA LAPANSI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIA LAPANSI AS

Who owns NIA LAPANSI AS?

Kamilla Schultz Seljelid is the largest registered owner, with 100.0%.

What is the revenue of NIA LAPANSI AS?

NIA LAPANSI AS had revenue of NOK 94,000 in 2025.

Who is the general manager of NIA LAPANSI AS?

Kamilla Schultz Seljelid is registered as general manager of NIA LAPANSI AS.

Where is NIA LAPANSI AS based?

NIA LAPANSI AS has its business address in Fornebu.

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.