biztrac. BETA
COMPANY REGISTER PROFILE
920008135 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of recreational and sports goods

LAPINI AS

Org. no. 920008135 Limited company (AS) Stange Incorporated 2017 Active
Revenue 2025 NOK 70,000
Operating profit NOK −135,000
Equity NOK −55,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−55k kr).

LAPINI AS is registered as a limited company in Stange, Innlandet with organisation number 920008135. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Investering i treningsutstyr og tilhørende utstyr for utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 70,000 in revenue and NOK −135,000 in operating profit.

Key figures · 2025

Revenue
NOK 70,000
▼ −58 %
Operating profit
NOK −135,000
▼ −6277 %
Equity
NOK −55,000
▼ −182 %

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
-21.5%
Not satisfactory
Return on total assets
Solidity
-9.4%
Weak
Equity as a share of total capital

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

Who owns LAPINI AS?

LAPINI AS
NOK 70,000 rev. · NOK −135,000 profit

LAPINI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAPINI AS

Who owns LAPINI AS?

Nina Lauvstad is the largest registered owner, with 100.0%.

What is the revenue of LAPINI AS?

LAPINI AS had revenue of NOK 70,000 in 2025.

Who is the general manager of LAPINI AS?

Nina Lauvstad is registered as general manager of LAPINI AS.

Where is LAPINI AS based?

LAPINI AS has its business address in Stange.

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.