BIZTRAC BETA
Other software publishing

NEVER NO AS

Org. no. 981063163 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 15.4m
Operating profit NOK 9.2m
Equity NOK 34.3m
Incorporated 1999
Share capital NOK 49.3m

Signals

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

NEVER NO AS is registered as a limited company in Oslo, Oslo with organisation number 981063163. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 1999. Registered share capital is NOK 49.3m, divided into 9860000 shares. The company's stated purpose is: “Produktutvikling og konsulentvirksomhet innen digitale kommunikasjonsløsninger for TV, mobiltelefon og Internett samt relatert virksomhet, inkludert deltagelse i andre selskaper og utleie av fast eiendom. ”. The most recent filed accounts, for the 2024 financial year, show NOK 15.4m in revenue and NOK 9.2m in operating profit.

Key figures · 2024

Revenue
NOK 15.4m
Operating profit
NOK 9.2m
Equity
NOK 34.3m
Est. value
NOK 52.0m

Financial health · 2024

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

Who owns NEVER NO AS?

HAVILA HOLDING AS
NEVER NO AS
NOK 15.4m rev. · NOK 9.2m profit

NEVER NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEVER NO AS

Who owns NEVER NO AS?

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

What is the revenue of NEVER NO AS?

NEVER NO AS had revenue of NOK 15.4m in 2024.

Who is the general manager of NEVER NO AS?

Edoardo Abis is registered as general manager of NEVER NO AS.

Where is NEVER NO AS based?

NEVER NO AS has its business address in Oslo.

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.