BIZTRAC BETA
Holiday and other short-stay accommodation

BESSO AS

Org. no. 990981221 Limited company (AS) Skien Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −2,000
Equity NOK 906,000
Incorporated 2007
Share capital NOK 90,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BESSO AS is registered as a limited company in Skien, Telemark with organisation number 990981221. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2007. Registered share capital is NOK 90,000, divided into 300 shares. The company's stated purpose is: “Drive turisthytte og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −2,000
Equity
NOK 906,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns BESSO AS?

FJELLVÅKEN HOLDING AS
BESSO AS
NOK 1.5m rev. · NOK −2,000 profit

BESSO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BESSO AS er morselskap for 28 datterselskaper:

Frequently asked questions about BESSO AS

Who owns BESSO AS?

FJELLVÅKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BESSO AS?

BESSO AS had revenue of NOK 1.5m in 2024.

Who is the general manager of BESSO AS?

Jan Tyssebotn is registered as general manager of BESSO AS.

Where is BESSO AS based?

BESSO AS has its business address in Skien.

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.