BIZTRAC BETA
COMPANY REGISTER PROFILE
920362516 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LINING HOLDING AS

Org. no. 920362516 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −111,000
Equity NOK 10.4m
Incorporated 2018
Share capital NOK 240,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−111k kr).

LINING HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 920362516. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 240,000, divided into 40000 shares. The company's stated purpose is: “Investere og eie aksjer og verdipapirer, samt det som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −111,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −111,000
Equity
NOK 10.4m
Est. value
NOK 10.3m

Financial health · 2024

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

Who owns LINING HOLDING AS?

INGER-ELIN KNUTSEN VON DER FEHR
LINING HOLDING AS
NOK 0 rev. · NOK −111,000 profit

LINING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LINING HOLDING AS own?

LINING HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LINING HOLDING AS

Who owns LINING HOLDING AS?

INGER-ELIN KNUTSEN VON DER FEHR is the largest registered owner, with 100.0%.

What is the revenue of LINING HOLDING AS?

LINING HOLDING AS had revenue of NOK 0 in 2024.

Where is LINING HOLDING AS based?

LINING HOLDING AS has its business address in Tromsø.

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.