BIZTRAC BETA
Computer programming activities

LITERATE AS

Org. no. 916915098 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK −2.0m
Equity NOK 2.4m
Incorporated 2016
Employees 7
Share capital NOK 63,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).
  • Nylig endring 2026-06-02 Aksjekapital registrert 2026-06-02.

LITERATE AS is registered as a limited company in Tromsø, Troms with organisation number 916915098. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 63,000, divided into 626039 shares. The company's stated purpose is: “Videreutvikle og selge tjenester som gjelder screening av språkvansker og dysleksi samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK −2.0m in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK −2.0m
Equity
NOK 2.4m
Est. value
NOK 9.5m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.5%
Good
Equity as a share of total capital

Who owns LITERATE AS?

TRUDE NERGÅRD-NILSSEN
LITERATE AS
NOK 5.0m rev. · NOK −2.0m profit

LITERATE AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about LITERATE AS

Who owns LITERATE AS?

TRUDE NERGÅRD-NILSSEN is the largest registered owner, with 49.9%.

What is the revenue of LITERATE AS?

LITERATE AS had revenue of NOK 5.0m in 2025.

Who is the general manager of LITERATE AS?

Bård Alexander Hall is registered as general manager of LITERATE AS.

Where is LITERATE AS based?

LITERATE AS has its business address in Tromsø.

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.