biztrac. BETA
COMPANY REGISTER PROFILE
936256597 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hotels and similar accommodation

YTTERSIA HOLDING AS

Org. no. 936256597 Limited company (AS) Senja Incorporated 2025 Active
Operating profit NOK −3
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3 kr).

YTTERSIA HOLDING AS is registered as a limited company in Senja, Troms with organisation number 936256597. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering, eierskap og forvaltning av selskaper, fast eiendom, finansielle aktiva og annen virksomhet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −3
Equity
NOK 30,000
Est. value
NOK 40,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
49.2%
Weak
Equity as a share of total capital

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

Who owns YTTERSIA HOLDING AS?

YTTERSIA HOLDING AS
· NOK −3 profit

YTTERSIA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does YTTERSIA HOLDING AS own?

YTTERSIA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about YTTERSIA HOLDING AS

Who owns YTTERSIA HOLDING AS?

Markus Bjørkli Jansen is the largest registered owner, with 100.0%.

Who is the general manager of YTTERSIA HOLDING AS?

Markus Bjørkli Jansen is registered as general manager of YTTERSIA HOLDING AS.

Where is YTTERSIA HOLDING AS based?

YTTERSIA HOLDING AS has its business address in Skaland.

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.