biztrac. BETA
COMPANY REGISTER PROFILE
916881827 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

EVENTYLON AS

Org. no. 916881827 Limited company (AS) Halden Incorporated 2016 Active
Revenue 2025 NOK 139,000
Operating profit NOK 17,000
Equity NOK −8,000
Incorporated 2016
Share capital NOK 330,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−8k 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 2025 financial year, show NOK 139,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 139,000
▲ +215 %
Operating profit
NOK 17,000
▲ +136 %
Equity
NOK −8,000
▲ +66 %

Financial health · 2025

Liquidity
1.71
Good
Current assets ÷ current liabilities
Profitability
63.1%
Very good
Return on total assets
Solidity
-23.4%
Weak
Equity as a share of total capital

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

Who owns EVENTYLON AS?

EVENTYLON AS
NOK 139,000 rev. · NOK 17,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 139,000 in 2025.

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

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.