BIZTRAC BETA
Other support activities to arts and performing arts

SEILET EVENTS AS

Org. no. 924536241 Limited company (AS) Holmestrand Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK −161,000
Equity NOK 125,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−161k kr).

SEILET EVENTS AS is registered as a limited company in Holmestrand, Vestfold with organisation number 924536241. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arrangere events som konserter, tilstelninger og andre lignende arrangement.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK −161,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK −161,000
Equity
NOK 125,000
Est. value
NOK 4.2m

Financial health · 2024

Liquidity
13.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
94.3%
Very good
Equity as a share of total capital

Who owns SEILET EVENTS AS?

KJETIL BØRDALEN-ELSTAD
SEILET EVENTS AS
NOK 4.1m rev. · NOK −161,000 profit

SEILET EVENTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEILET EVENTS AS

Who owns SEILET EVENTS AS?

KJETIL BØRDALEN-ELSTAD is the largest registered owner, with 100.0%.

What is the revenue of SEILET EVENTS AS?

SEILET EVENTS AS had revenue of NOK 4.1m in 2024.

Who is the general manager of SEILET EVENTS AS?

Kjetil Børdalen-Elstad is registered as general manager of SEILET EVENTS AS.

Where is SEILET EVENTS AS based?

SEILET EVENTS AS has its business address in Sande I Vestfold.

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.