BIZTRAC BETA
Restaurant activities

MATHUSET LOFOTEN AS

Org. no. 995216523 Limited company (AS) Vågan Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 3.7m
Equity NOK 2.4m
Incorporated 2010
Share capital NOK 330,000

MATHUSET LOFOTEN AS is registered as a limited company in Vågan, Nordland with organisation number 995216523. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2010. Registered share capital is NOK 330,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom, samt investering i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 3.7m
Equity
NOK 2.4m
Est. value
NOK 12.0m

Financial health · 2025

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

Who owns MATHUSET LOFOTEN AS?

SIV HILDE TORMODSDATTER LILLEHAUG
MATHUSET LOFOTEN AS
NOK 3.9m rev. · NOK 3.7m profit

MATHUSET LOFOTEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MATHUSET LOFOTEN AS own?

MATHUSET LOFOTEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MATHUSET LOFOTEN AS

Who owns MATHUSET LOFOTEN AS?

SIV HILDE TORMODSDATTER LILLEHAUG is the largest registered owner, with 50.0%.

What is the revenue of MATHUSET LOFOTEN AS?

MATHUSET LOFOTEN AS had revenue of NOK 3.9m in 2025.

Who is the general manager of MATHUSET LOFOTEN AS?

Siv Hilde Tormodsdatter Lillehaug is registered as general manager of MATHUSET LOFOTEN AS.

Where is MATHUSET LOFOTEN AS based?

MATHUSET LOFOTEN AS has its business address in Henningsvær.

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.