BIZTRAC BETA
Marine fishing

STIAN ANDRE AS

Org. no. 917418500 Limited company (AS) Lyngen Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 15.1m
Operating profit NOK −281,000
Equity NOK 10.6m
Incorporated 2016
Share capital NOK 500,000

Signals

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

STIAN ANDRE AS is registered as a limited company in Lyngen, Troms with organisation number 917418500. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2016. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Eie og drive fiskefartøy samt investere i andre selskaper og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.1m in revenue and NOK −281,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.1m
Operating profit
NOK −281,000
Equity
NOK 10.6m
Est. value
NOK 10.1m

Financial health · 2024

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

Who owns STIAN ANDRE AS?

BØRGE HANSEN
STIAN ANDRE AS
NOK 15.1m rev. · NOK −281,000 profit

STIAN ANDRE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STIAN ANDRE AS own?

STIAN ANDRE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STIAN ANDRE AS

Who owns STIAN ANDRE AS?

BØRGE HANSEN is the largest registered owner, with 55.0%.

What is the revenue of STIAN ANDRE AS?

STIAN ANDRE AS had revenue of NOK 15.1m in 2024.

Who is the general manager of STIAN ANDRE AS?

Børge Hansen is registered as general manager of STIAN ANDRE AS.

Where is STIAN ANDRE AS based?

STIAN ANDRE AS has its business address in Nord-Lenangen.

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.