BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

ISNA AS

Org. no. 913425898 Limited company (AS) Ålesund Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 60,000
Operating profit NOK −18,000
Equity NOK 532,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

ISNA AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 913425898. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering og deltakelse i andre virksomheter samt konsulentvirksomhet og båtutleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 60,000 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 60,000
Operating profit
NOK −18,000
Equity
NOK 532,000
Est. value
NOK 323,000

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.6%
Very good
Equity as a share of total capital

Who owns ISNA AS?

INGE SVENN NÆRØ
ISNA AS
NOK 60,000 rev. · NOK −18,000 profit

ISNA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ISNA AS own?

ISNA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ISNA AS

Who owns ISNA AS?

INGE SVENN NÆRØ is the largest registered owner, with 100.0%.

What is the revenue of ISNA AS?

ISNA AS had revenue of NOK 60,000 in 2025.

Who is the general manager of ISNA AS?

Inge Svenn Nærø is registered as general manager of ISNA AS.

Where is ISNA AS based?

ISNA AS has its business address in Ålesund.

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.