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

GURMAN AS

Org. no. 932861534 Limited company (AS) Trondheim Incorporated 2023 Active
Revenue 2025 NOK 1.9m
Operating profit NOK −83,000
Equity NOK −163,000
Incorporated 2023
Employees 10
Share capital NOK 30,000

Signals

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

GURMAN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932861534. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Jobbe i serveringsbransjen med ideen for å promotere kroatisk og balkan mat.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −83,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +130 %
Operating profit
NOK −83,000
▲ +4 %
Equity
NOK −163,000
▼ −121 %

Financial health · 2025

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
-29.1%
Not satisfactory
Return on total assets
Solidity
-39.4%
Weak
Equity as a share of total capital

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

Who owns GURMAN AS?

GURMAN AS
NOK 1.9m rev. · NOK −83,000 profit

GURMAN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GURMAN AS

Who owns GURMAN AS?

Denis Uhoda is the largest registered owner, with 50.0%.

What is the revenue of GURMAN AS?

GURMAN AS had revenue of NOK 1.9m in 2025.

Who is the general manager of GURMAN AS?

Denis Uhoda is registered as general manager of GURMAN AS.

Where is GURMAN AS based?

GURMAN AS has its business address in Trondheim.

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.