BIZTRAC BETA
Restaurant activities

VERTSHUSET GIBOSTAD AS

Org. no. 916349955 Limited company (AS) Senja Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 751,000
Operating profit NOK 44,000
Equity NOK 104,000
Incorporated 2015
Share capital NOK 300,000

VERTSHUSET GIBOSTAD AS is registered as a limited company in Senja, Troms with organisation number 916349955. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Drift av vertshus, pub og uteservering, utleie av selskapslokaler, samt hva som står i forbindelse med dette, herunder deltagelse i andre foretagender med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 751,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2024

Revenue
NOK 751,000
Operating profit
NOK 44,000
Equity
NOK 104,000
Est. value
NOK 215,000

Financial health · 2024

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.7%
Good
Equity as a share of total capital

Who owns VERTSHUSET GIBOSTAD AS?

TOR EGIL SEBULONSEN
VERTSHUSET GIBOSTAD AS
NOK 751,000 rev. · NOK 44,000 profit

VERTSHUSET GIBOSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VERTSHUSET GIBOSTAD AS

Who owns VERTSHUSET GIBOSTAD AS?

TOR EGIL SEBULONSEN is the largest registered owner, with 100.0%.

What is the revenue of VERTSHUSET GIBOSTAD AS?

VERTSHUSET GIBOSTAD AS had revenue of NOK 751,000 in 2024.

Who is the general manager of VERTSHUSET GIBOSTAD AS?

Tor Egil Sebulonsen is registered as general manager of VERTSHUSET GIBOSTAD AS.

Where is VERTSHUSET GIBOSTAD AS based?

VERTSHUSET GIBOSTAD AS has its business address in Gibostad.

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.