BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

LIRO DRIFT AS

Org. no. 998314666 Limited company (AS) Harstad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 472,000
Operating profit NOK 40,000
Equity NOK 56,000
Incorporated 2012
Share capital NOK 70,000

LIRO DRIFT AS is registered as a limited company in Harstad, Troms with organisation number 998314666. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2012. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Kjøp og salg av varer, samt distribusjon og andre tjenester som naturlig hører sammen med dette. I tillegg skal selskapet kunne delta i annen virksomhet med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 472,000 in revenue and NOK 40,000 in operating profit.

Key figures · 2025

Revenue
NOK 472,000
Operating profit
NOK 40,000
Equity
NOK 56,000
Est. value
NOK 90,000

Financial health · 2025

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

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

Who owns LIRO DRIFT AS?

LINDA KAROLINE STEINBAKK HANSEN
LIRO DRIFT AS
NOK 472,000 rev. · NOK 40,000 profit

LIRO DRIFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIRO DRIFT AS

Who owns LIRO DRIFT AS?

LINDA KAROLINE STEINBAKK HANSEN is the largest registered owner, with 57.1%.

What is the revenue of LIRO DRIFT AS?

LIRO DRIFT AS had revenue of NOK 472,000 in 2025.

Who is the general manager of LIRO DRIFT AS?

Robert Hansen is registered as general manager of LIRO DRIFT AS.

Where is LIRO DRIFT AS based?

LIRO DRIFT AS has its business address in Sørvik.

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.