BIZTRAC BETA
Other business support service activities n.e.c.

AVSETH AKTIV AS

Org. no. 996702332 Limited company (AS) Giske Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −253,000
Equity NOK 1.6m
Incorporated 2011
Share capital NOK 100,000

Signals

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

AVSETH AKTIV AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 996702332. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Båtmegling, kjøp og salg av båt- og båtutstyr, fiskerivirksomhet, kjøp og salg av fisk, samt øvrig virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −253,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −253,000
Equity
NOK 1.6m
Est. value
NOK 996,000

Financial health · 2024

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

Who owns AVSETH AKTIV AS?

AVSETH AS
AVSETH AKTIV AS
NOK 1.1m rev. · NOK −253,000 profit

AVSETH AKTIV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AVSETH AKTIV AS

Who owns AVSETH AKTIV AS?

AVSETH AS is the largest registered owner, with 100.0%.

What is the revenue of AVSETH AKTIV AS?

AVSETH AKTIV AS had revenue of NOK 1.1m in 2024.

Who is the general manager of AVSETH AKTIV AS?

Svein Ove Avseth is registered as general manager of AVSETH AKTIV AS.

Where is AVSETH AKTIV AS based?

AVSETH AKTIV AS has its business address in Giske.

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.