BIZTRAC BETA
Computer programming activities

EVENTERING AS

Org. no. 920364195 Limited company (AS) Lillehammer Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 240,000
Operating profit NOK −608,000
Equity NOK −1.5m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−608k kr).

EVENTERING AS is registered as a limited company in Lillehammer, Innlandet with organisation number 920364195. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie, utvikle og videreselge programvare og det som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 240,000 in revenue and NOK −608,000 in operating profit.

Key figures · 2025

Revenue
NOK 240,000
Operating profit
NOK −608,000
Equity
NOK −1.5m

Financial health · 2025

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

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

Who owns EVENTERING AS?

PROSIT AS
EVENTERING AS
NOK 240,000 rev. · NOK −608,000 profit

EVENTERING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EVENTERING AS

Who owns EVENTERING AS?

PROSIT AS is the largest registered owner, with 33.3%.

What is the revenue of EVENTERING AS?

EVENTERING AS had revenue of NOK 240,000 in 2025.

Who is the general manager of EVENTERING AS?

Arthur Glenne is registered as general manager of EVENTERING AS.

Where is EVENTERING AS based?

EVENTERING 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.