BIZTRAC BETA
Restaurant activities

DIGGIN FOODTRUCK AS

Org. no. 917762821 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 335,000
Equity NOK −94,000
Incorporated 2016
Employees 12
Share capital NOK 83,000

Signals

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

DIGGIN FOODTRUCK AS is registered as a limited company in Haugesund, Rogaland with organisation number 917762821. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016 and has 12 registered employees. Registered share capital is NOK 83,000, divided into 2750 shares. The company's stated purpose is: “Salg av mat fra mobil Van.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 335,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 335,000
Equity
NOK −94,000
Est. value
NOK 2.5m

Financial health · 2024

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

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

Who owns DIGGIN FOODTRUCK AS?

REGINE BREIVIK GRØNHAUG
DIGGIN FOODTRUCK AS
NOK 7.0m rev. · NOK 335,000 profit

DIGGIN FOODTRUCK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIGGIN FOODTRUCK AS

Who owns DIGGIN FOODTRUCK AS?

REGINE BREIVIK GRØNHAUG is the largest registered owner, with 50.0%.

What is the revenue of DIGGIN FOODTRUCK AS?

DIGGIN FOODTRUCK AS had revenue of NOK 7.0m in 2024.

Who is the general manager of DIGGIN FOODTRUCK AS?

Linn Anita Tryggestad is registered as general manager of DIGGIN FOODTRUCK AS.

Where is DIGGIN FOODTRUCK AS based?

DIGGIN FOODTRUCK AS has its business address in Haugesund.

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.