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

SPISEKROKEN INGVILD AS

Org. no. 979942400 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 15.1m
Operating profit NOK 105,000
Equity NOK 6.5m
Incorporated 1998
Employees 46
Share capital NOK 100,000

SPISEKROKEN INGVILD AS is registered as a limited company in Bergen, Vestland with organisation number 979942400. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1998 and has 46 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Restaurantdrift og alt annet som faller inn under denne virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.1m in revenue and NOK 105,000 in operating profit.

Key figures · 2025

Revenue
NOK 15.1m
▼ −11 %
Operating profit
NOK 105,000
▼ −92 %
Equity
NOK 6.5m
▲ +3 %
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
3.55
Very good
Current assets ÷ current liabilities
Profitability
2.9%
Weak
Return on total assets
Solidity
78.0%
Very good
Equity as a share of total capital

Who owns SPISEKROKEN INGVILD AS?

SPISEKROKEN INGVILD AS
NOK 15.1m rev. · NOK 105,000 profit

SPISEKROKEN INGVILD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPISEKROKEN INGVILD AS

Who owns SPISEKROKEN INGVILD AS?

Ingvild Tone Skorpen Bøge is the largest registered owner, with 100.0%.

What is the revenue of SPISEKROKEN INGVILD AS?

SPISEKROKEN INGVILD AS had revenue of NOK 15.1m in 2025.

Who is the general manager of SPISEKROKEN INGVILD AS?

Ingvild Tone Skorpen Bøge is registered as general manager of SPISEKROKEN INGVILD AS.

Where is SPISEKROKEN INGVILD AS based?

SPISEKROKEN INGVILD 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.