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

HOLTEBU HOLDING AS

Org. no. 916863470 Limited company (AS) Moss Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −112,000
Equity NOK 11.0m
Incorporated 2016
Share capital NOK 130,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−112k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HOLTEBU HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 916863470. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016. Registered share capital is NOK 130,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper og sammenslutninger, og aktiviteter i naturlige sammenheng med dette.”.

Key figures · 2025

Operating profit
NOK −112,000
▲ +7 %
Equity
NOK 11.0m
▲ +11 %
Est. value
NOK 31.5m

Financial health · 2025

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

Who owns HOLTEBU HOLDING AS?

HOLTEBU HOLDING AS
· NOK −112,000 profit

HOLTEBU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOLTEBU HOLDING AS own?

HOLTEBU HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about HOLTEBU HOLDING AS

Who owns HOLTEBU HOLDING AS?

OWE HOLTEBU is the largest registered owner, with 100.0%.

Who is the general manager of HOLTEBU HOLDING AS?

Owe Holtebu is registered as general manager of HOLTEBU HOLDING AS.

Where is HOLTEBU HOLDING AS based?

HOLTEBU HOLDING AS has its business address in Moss.

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.