BIZTRAC BETA
Retail sale of furniture, including mattresses and box springs

LDB HOLDING AS

Org. no. 918413669 Limited company (AS) Harstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −73
Equity NOK 500,000
Incorporated 2016
Share capital NOK 510,000

Signals

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

LDB HOLDING AS is registered as a limited company in Harstad, Troms with organisation number 918413669. The business is classified under retail sale of furniture, including mattresses and box springs (NACE 47.551). The company was incorporated in 2016. Registered share capital is NOK 510,000, divided into 510 shares. The company's stated purpose is: “Konsulentvirksomhet, investeringer, garantistillelser og deltakelse i andre selskap og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −73 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −73
Equity
NOK 500,000
Est. value
NOK 3.0m

Financial health · 2025

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

Who owns LDB HOLDING AS?

LEIF DANIEL BÄCKSTRÖM
LDB HOLDING AS
NOK 0 rev. · NOK −73 profit

LDB HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LDB HOLDING AS own?

LDB HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LDB HOLDING AS

Who owns LDB HOLDING AS?

LEIF DANIEL BÄCKSTRÖM is the largest registered owner, with 100.0%.

What is the revenue of LDB HOLDING AS?

LDB HOLDING AS had revenue of NOK 0 in 2025.

Where is LDB HOLDING AS based?

LDB HOLDING AS has its business address in Harstad.

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.