BIZTRAC BETA
Activities of excursion and event organisers

BUSI EXPERIENCE AS

Org. no. 933905292 Limited company (AS) Trysil Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 6,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

BUSI EXPERIENCE AS is registered as a limited company in Trysil, Innlandet with organisation number 933905292. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med events relatert til sport og selger opplevelser.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 6,000
Est. value
NOK 8,000

Financial health · 2024

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

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

Who owns BUSI EXPERIENCE AS?

WILLIAM ØDEGAARD KALFOSS
BUSI EXPERIENCE AS
NOK 0 rev. · NOK −18,000 profit

BUSI EXPERIENCE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BUSI EXPERIENCE AS

Who owns BUSI EXPERIENCE AS?

WILLIAM ØDEGAARD KALFOSS is the largest registered owner, with 50.0%.

What is the revenue of BUSI EXPERIENCE AS?

BUSI EXPERIENCE AS had revenue of NOK 0 in 2024.

Who is the general manager of BUSI EXPERIENCE AS?

William Ødegaard Kalfoss is registered as general manager of BUSI EXPERIENCE AS.

Where is BUSI EXPERIENCE AS based?

BUSI EXPERIENCE AS has its business address in Trysil.

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.