BIZTRAC BETA
Removal services

DINFLYTTING AS

Org. no. 916561393 Limited company (AS) Harstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK −146,000
Equity NOK 567,000
Incorporated 2016
Employees 7
Share capital NOK 30,000

Signals

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

DINFLYTTING AS is registered as a limited company in Harstad, Troms with organisation number 916561393. The business is classified under removal services (NACE 49.420). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Flytteservice, frakt, utleie av lager, utleie og leasing av biler, varebiler, lastebiler, hengere og andre lette motorvogner, Eiendom, kjøp av konkursbo, vareparti samt renholdstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK −146,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK −146,000
Equity
NOK 567,000
Est. value
NOK 296,000

Financial health · 2024

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

Who owns DINFLYTTING AS?

LEIF-BØRRE LIND
DINFLYTTING AS
NOK 4.2m rev. · NOK −146,000 profit

DINFLYTTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DINFLYTTING AS

Who owns DINFLYTTING AS?

LEIF-BØRRE LIND is the largest registered owner, with 100.0%.

What is the revenue of DINFLYTTING AS?

DINFLYTTING AS had revenue of NOK 4.2m in 2024.

Who is the general manager of DINFLYTTING AS?

Leif-Børre Lind is registered as general manager of DINFLYTTING AS.

Where is DINFLYTTING AS based?

DINFLYTTING 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.