BIZTRAC BETA
Uoppgitt

LINDEFLATEN HOLDING AS

Org. no. 926149385 Limited company (AS) Moss Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 19,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

LINDEFLATEN HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 926149385. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 19,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns LINDEFLATEN HOLDING AS?

ARILD LINDEFLATEN
LINDEFLATEN HOLDING AS
· NOK −5,000 profit

LINDEFLATEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LINDEFLATEN HOLDING AS own?

LINDEFLATEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LINDEFLATEN HOLDING AS

Who owns LINDEFLATEN HOLDING AS?

ARILD LINDEFLATEN is the largest registered owner, with 100.0%.

Who is the general manager of LINDEFLATEN HOLDING AS?

Arild Lindeflaten is registered as general manager of LINDEFLATEN HOLDING AS.

Where is LINDEFLATEN HOLDING AS based?

LINDEFLATEN HOLDING AS has its business address in Moss.

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.