BIZTRAC BETA
Restaurant activities

MATROSEN PUB & SPISERI AS

Org. no. 927721325 Limited company (AS) Frøya Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 105,000
Equity NOK 609,000
Incorporated 2021
Share capital NOK 560,000

MATROSEN PUB & SPISERI AS is registered as a limited company in Frøya, Trøndelag with organisation number 927721325. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021. Registered share capital is NOK 560,000, divided into 560 shares. The company's stated purpose is: “Restaurantvirksomhet med salg av mat, øl, vin innen- og utendørs, samt produksjon og salg av take away-mat. Også overnattingstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 105,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 105,000
Equity
NOK 609,000
Est. value
NOK 639,000

Financial health · 2024

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

Who owns MATROSEN PUB & SPISERI AS?

JOAR SIGURD JOHANSEN
MATROSEN PUB & SPISERI AS
NOK 1.6m rev. · NOK 105,000 profit

MATROSEN PUB & SPISERI AS has 10 registered shareholders:

All shareholders and roles →

Frequently asked questions about MATROSEN PUB & SPISERI AS

Who owns MATROSEN PUB & SPISERI AS?

JOAR SIGURD JOHANSEN is the largest registered owner, with 39.3%.

What is the revenue of MATROSEN PUB & SPISERI AS?

MATROSEN PUB & SPISERI AS had revenue of NOK 1.6m in 2024.

Who is the general manager of MATROSEN PUB & SPISERI AS?

Rannveig Slettun is registered as general manager of MATROSEN PUB & SPISERI AS.

Where is MATROSEN PUB & SPISERI AS based?

MATROSEN PUB & SPISERI AS has its business address in Mausund.

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.