BIZTRAC BETA
Restaurant activities

JOHN B AS

Org. no. 924844868 Limited company (AS) Hamar Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 242,000
Equity NOK −1.1m
Incorporated 2020
Employees 16
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).

JOHN B AS is registered as a limited company in Hamar, Innlandet with organisation number 924844868. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen restaurant, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 242,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 242,000
Equity
NOK −1.1m
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-309.6%
Weak
Equity as a share of total capital

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

Who owns JOHN B AS?

ÅSE MARGIT MIDTVEIT
JOHN B AS
NOK 6.3m rev. · NOK 242,000 profit

JOHN B AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOHN B AS

Who owns JOHN B AS?

ÅSE MARGIT MIDTVEIT is the largest registered owner, with 50.0%.

What is the revenue of JOHN B AS?

JOHN B AS had revenue of NOK 6.3m in 2025.

Who is the general manager of JOHN B AS?

Åse Margit Midtveit is registered as general manager of JOHN B AS.

Where is JOHN B AS based?

JOHN B AS has its business address in Hamar.

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.