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

NEBBENES KROER AS

Org. no. 948727277 Limited company (AS) Eidsvoll Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 33.2m
Operating profit NOK −594,000
Equity NOK 4.9m
Incorporated 1988
Employees 71
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−594k kr).

NEBBENES KROER AS is registered as a limited company in Eidsvoll, Akershus with organisation number 948727277. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1988 and has 71 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Drift av serveringssted og hva som står i forbind- else med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.2m in revenue and NOK −594,000 in operating profit.

Key figures · 2025

Revenue
NOK 33.2m
Operating profit
NOK −594,000
Equity
NOK 4.9m
Est. value
NOK 22.8m

Financial health · 2025

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

Who owns NEBBENES KROER AS?

NEBBENES KROER AS
NOK 33.2m rev. · NOK −594,000 profit

NEBBENES KROER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEBBENES KROER AS

Who owns NEBBENES KROER AS?

NEBBENES AS is the largest registered owner, with 100.0%.

What is the revenue of NEBBENES KROER AS?

NEBBENES KROER AS had revenue of NOK 33.2m in 2025.

Who is the general manager of NEBBENES KROER AS?

Per Nebbenes is registered as general manager of NEBBENES KROER AS.

Where is NEBBENES KROER AS based?

NEBBENES KROER AS has its business address in Eidsvoll Verk.

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.