BIZTRAC BETA
Computer programming activities

EVENTYLON AS

Org. no. 916881827 Limited company (AS) Halden Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 44,000
Operating profit NOK −47,000
Equity NOK −23,000
Incorporated 2016
Share capital NOK 330,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−23k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−47k kr).

EVENTYLON AS is registered as a limited company in Halden, Østfold with organisation number 916881827. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016. Registered share capital is NOK 330,000, divided into 11000 shares. The company's stated purpose is: “Salg og utvikling av programvare og tjenester relatert til organisering av arrangementer.”. The most recent filed accounts, for the 2024 financial year, show NOK 44,000 in revenue and NOK −47,000 in operating profit.

Key figures · 2024

Revenue
NOK 44,000
Operating profit
NOK −47,000
Equity
NOK −23,000

Financial health · 2024

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

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

Who owns EVENTYLON AS?

MARIUS BJUGAN
EVENTYLON AS
NOK 44,000 rev. · NOK −47,000 profit

EVENTYLON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EVENTYLON AS

Who owns EVENTYLON AS?

MARIUS BJUGAN is the largest registered owner, with 100.0%.

What is the revenue of EVENTYLON AS?

EVENTYLON AS had revenue of NOK 44,000 in 2024.

Who is the general manager of EVENTYLON AS?

Marius Bjugan is registered as general manager of EVENTYLON AS.

Where is EVENTYLON AS based?

EVENTYLON AS has its business address in Halden.

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.