BIZTRAC BETA
Restaurant activities

TROMSØ JERNBANESTASJON AS

Org. no. 995190923 Limited company (AS) Tromsø Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 20.1m
Operating profit NOK 1.5m
Equity NOK 1.3m
Incorporated 2010
Employees 22
Share capital NOK 1.0m

TROMSØ JERNBANESTASJON AS is registered as a limited company in Tromsø, Troms with organisation number 995190923. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2010 and has 22 registered employees. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Å drive pub/restaurantvirksomhet og det som hermed står i forbindelse. I tillegg drive handel samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.1m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 20.1m
Operating profit
NOK 1.5m
Equity
NOK 1.3m
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.7%
Good
Equity as a share of total capital

Who owns TROMSØ JERNBANESTASJON AS?

FUN PUB TROMSØ AS
TROMSØ JERNBANESTASJON AS
NOK 20.1m rev. · NOK 1.5m profit

TROMSØ JERNBANESTASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROMSØ JERNBANESTASJON AS

Who owns TROMSØ JERNBANESTASJON AS?

FUN PUB TROMSØ AS is the largest registered owner, with 100.0%.

What is the revenue of TROMSØ JERNBANESTASJON AS?

TROMSØ JERNBANESTASJON AS had revenue of NOK 20.1m in 2025.

Who is the general manager of TROMSØ JERNBANESTASJON AS?

Harry Granås is registered as general manager of TROMSØ JERNBANESTASJON AS.

Where is TROMSØ JERNBANESTASJON AS based?

TROMSØ JERNBANESTASJON AS has its business address in Tromsø.

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.