biztrac. BETA
COMPANY REGISTER PROFILE
924685484 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

MORMORS AS

Org. no. 924685484 Limited company (AS) Hadsel Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK −611,000
Equity NOK −1.3m
Incorporated 2020
Employees 17
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−611k kr).

MORMORS AS is registered as a limited company in Hadsel, Nordland with organisation number 924685484. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av egenprodusert mat og drikke samt håndverk fra lokale leverandører.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK −611,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
▲ +4 %
Operating profit
NOK −611,000
▼ −658 %
Equity
NOK −1.3m
▼ −114 %

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
-166.7%
Not satisfactory
Return on total assets
Solidity
-379.0%
Weak
Equity as a share of total capital

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

Who owns MORMORS AS?

MORMORS AS
NOK 3.8m rev. · NOK −611,000 profit

MORMORS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MORMORS AS

Who owns MORMORS AS?

Bodil Bergvik Vestgård is the largest registered owner, with 50.0%.

What is the revenue of MORMORS AS?

MORMORS AS had revenue of NOK 3.8m in 2025.

Where is MORMORS AS based?

MORMORS AS has its business address in Stokmarknes.

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.