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

HANGRY HUB AS

Org. no. 936596142 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 821,000
Operating profit NOK 95,000
Equity NOK 588,000
Incorporated 2025
Employees 19
Share capital NOK 500,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-03.

HANGRY HUB AS is registered as a limited company in Bergen, Vestland with organisation number 936596142. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025 and has 19 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Drift av restaurant samt, salg av produkter som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 821,000 in revenue and NOK 95,000 in operating profit.

Key figures · 2025

Revenue
NOK 821,000
Operating profit
NOK 95,000
Equity
NOK 588,000
Est. value
NOK 696,000

Financial health · 2025

Liquidity
1.99
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
49.1%
Very good
Equity as a share of total capital

Who owns HANGRY HUB AS?

HANGRY HUB AS
NOK 821,000 rev. · NOK 95,000 profit

HANGRY HUB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HANGRY HUB AS

Who owns HANGRY HUB AS?

HANGRY INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HANGRY HUB AS?

HANGRY HUB AS had revenue of NOK 821,000 in 2025.

Who is the general manager of HANGRY HUB AS?

Sharon Femmigje Adriana Doldersum is registered as general manager of HANGRY HUB AS.

Where is HANGRY HUB AS based?

HANGRY HUB AS has its business address in Bergen.

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.