BIZTRAC BETA
COMPANY REGISTER PROFILE
930514225 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Restaurant activities

BURGER HANA AS

Org. no. 930514225 Limited company (AS) Sandnes Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 8,000
Equity NOK 100,000
Incorporated 2022
Employees 14
Share capital NOK 100,000

BURGER HANA AS is registered as a limited company in Sandnes, Rogaland with organisation number 930514225. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 14 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handelsvirksomhet, tjenesteytende virksomhet, samt hva herved står i forbindelse, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
▲ +3 %
Operating profit
NOK 8,000
▲ +107 %
Equity
NOK 100,000
▲ +332 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
1.78
Good
Current assets ÷ current liabilities
Profitability
0.3%
Not satisfactory
Return on total assets
Solidity
3.7%
Weak
Equity as a share of total capital

Who owns BURGER HANA AS?

BURGER HANA AS
NOK 4.9m rev. · NOK 8,000 profit

BURGER HANA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BURGER HANA AS

Who owns BURGER HANA AS?

THE SHACK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BURGER HANA AS?

BURGER HANA AS had revenue of NOK 4.9m in 2025.

Who is the general manager of BURGER HANA AS?

Gunnar Bernt Schem Ellingsen is registered as general manager of BURGER HANA AS.

Where is BURGER HANA AS based?

BURGER HANA AS has its business address in Sandnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.