BIZTRAC BETA
Wholesale of household, office and shop furniture, carpets and lighting equipment

LINDBAK INTERIØR AS

Org. no. 933908348 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 19,000
Incorporated 2024
Employees 127
Share capital NOK 90,000

Signals

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

LINDBAK INTERIØR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 933908348. The business is classified under wholesale of household, office and shop furniture, carpets and lighting equipment (NACE 46.470). The company was incorporated in 2024 and has 127 registered employees. Registered share capital is NOK 90,000, divided into 100 shares. The company's stated purpose is: “Salg av kontorutstyr og hva som står i forbindelse med det.”.

Key figures · 2024

Operating profit
NOK −8,000
Equity
NOK 19,000
Est. value
NOK 24,000

Financial health · 2024

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.4%
Weak
Equity as a share of total capital

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

Who owns LINDBAK INTERIØR AS?

LINDBAK AS
LINDBAK INTERIØR AS
· NOK −8,000 profit

LINDBAK INTERIØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LINDBAK INTERIØR AS own?

LINDBAK INTERIØR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LINDBAK INTERIØR AS

Who owns LINDBAK INTERIØR AS?

LINDBAK AS is the largest registered owner, with 100.0%.

Who is the general manager of LINDBAK INTERIØR AS?

Jan Petter Dalgleish Lindbak is registered as general manager of LINDBAK INTERIØR AS.

Where is LINDBAK INTERIØR AS based?

LINDBAK INTERIØR AS has its business address in Trondheim.

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.