BIZTRAC BETA
Retail sale of medical and orthopaedic goods

LÅN HOLDING AS

Org. no. 918532250 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −1.7m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,7 mill kr).

LÅN HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 918532250. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −1.7m

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-71.2%
Weak
Equity as a share of total capital

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

Who owns LÅN HOLDING AS?

LISA NORDBOTN
LÅN HOLDING AS
NOK 0 rev. · NOK 0 profit

LÅN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LÅN HOLDING AS own?

LÅN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LÅN HOLDING AS

Who owns LÅN HOLDING AS?

LISA NORDBOTN is the largest registered owner, with 100.0%.

What is the revenue of LÅN HOLDING AS?

LÅN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of LÅN HOLDING AS?

Lisa Nordbotn is registered as general manager of LÅN HOLDING AS.

Where is LÅN HOLDING AS based?

LÅN HOLDING AS has its business address in Asker.

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.