BIZTRAC BETA
Computer programming activities

KODES AS

Org. no. 919362073 Limited company (AS) Lillehammer Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 896,000
Operating profit NOK 136,000
Equity NOK −173,000
Incorporated 2017
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−173k kr).

KODES AS is registered as a limited company in Lillehammer, Innlandet with organisation number 919362073. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 5000 shares. The company's stated purpose is: “Utvikling av hjemmesider på internett og nettbutikker, drift av disse og annen grafisk virksomhet og tjenesteyting som naturlig kommer i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 896,000 in revenue and NOK 136,000 in operating profit.

Key figures · 2024

Revenue
NOK 896,000
Operating profit
NOK 136,000
Equity
NOK −173,000
Est. value
NOK 1.5m

Financial health · 2024

Liquidity
0.55
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-100.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KODES AS?

TARJEI AUNE MYKLEBUST
KODES AS
NOK 896,000 rev. · NOK 136,000 profit

KODES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KODES AS

Who owns KODES AS?

TARJEI AUNE MYKLEBUST is the largest registered owner, with 60.0%.

What is the revenue of KODES AS?

KODES AS had revenue of NOK 896,000 in 2024.

Who is the general manager of KODES AS?

Tarjei Aune Myklebust is registered as general manager of KODES AS.

Where is KODES AS based?

KODES AS has its business address in Lillehammer.

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.