BIZTRAC BETA
Other software publishing

NYNODATA AS

Org. no. 848373672 Limited company (AS) Nome Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −112,000
Equity NOK 300,000
Incorporated 1988
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−112k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NYNODATA AS is registered as a limited company in Nome, Telemark with organisation number 848373672. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 1988. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Verksemda til selskapet er å drive utvikling og sal av språkteknologiske produkt, med vekt på nynorsk.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −112,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −112,000
Equity
NOK 300,000
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns NYNODATA AS?

SOLY GROUP AS
NYNODATA AS
NOK 1.3m rev. · NOK −112,000 profit

NYNODATA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYNODATA AS

Who owns NYNODATA AS?

SOLY GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of NYNODATA AS?

NYNODATA AS had revenue of NOK 1.3m in 2025.

Who is the general manager of NYNODATA AS?

Torstein Vogsland Gustavsen is registered as general manager of NYNODATA AS.

Where is NYNODATA AS based?

NYNODATA AS has its business address in Ulefoss.

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.