BIZTRAC BETA
Marine fishing

ASBJØRN SELSBANE AS

Org. no. 959908214 Limited company (AS) Tromsø Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 88.8m
Operating profit NOK 10.3m
Equity NOK 127.2m
Incorporated 1991
Share capital NOK 929,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASBJØRN SELSBANE AS is registered as a limited company in Tromsø, Troms with organisation number 959908214. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 1991. Registered share capital is NOK 929,000, divided into 929 shares. The company's stated purpose is: “Drive fiske og fangst samt annen virksomhet som naturlig faller inn under dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 88.8m in revenue and NOK 10.3m in operating profit.

Key figures · 2024

Revenue
NOK 88.8m
Operating profit
NOK 10.3m
Equity
NOK 127.2m
Est. value
NOK 86.2m

Financial health · 2024

Liquidity
2.43
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.4%
Good
Equity as a share of total capital

Who owns ASBJØRN SELSBANE AS?

AX HOLDING AS
ASBJØRN SELSBANE AS
NOK 88.8m rev. · NOK 10.3m profit

ASBJØRN SELSBANE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASBJØRN SELSBANE AS

Who owns ASBJØRN SELSBANE AS?

AX HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ASBJØRN SELSBANE AS?

ASBJØRN SELSBANE AS had revenue of NOK 88.8m in 2024.

Who is the general manager of ASBJØRN SELSBANE AS?

Andreas Kristoffer Hansen is registered as general manager of ASBJØRN SELSBANE AS.

Where is ASBJØRN SELSBANE AS based?

ASBJØRN SELSBANE AS has its business address in Kvaløya.

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.