BIZTRAC BETA
Beverage serving activities

OLAVS PUB AS

Org. no. 964706840 Limited company (AS) Sarpsborg Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK −136,000
Equity NOK −258,000
Incorporated 1992
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−258k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−136k kr).

OLAVS PUB AS is registered as a limited company in Sarpsborg, Østfold with organisation number 964706840. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Restaurantvirksomhet og alt som hermed står i naturlig forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK −136,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK −136,000
Equity
NOK −258,000

Financial health · 2025

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

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

Who owns OLAVS PUB AS?

ROLVSØY ØLVERKSTED AS
OLAVS PUB AS
NOK 3.2m rev. · NOK −136,000 profit

OLAVS PUB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAVS PUB AS

Who owns OLAVS PUB AS?

ROLVSØY ØLVERKSTED AS is the largest registered owner, with 100.0%.

What is the revenue of OLAVS PUB AS?

OLAVS PUB AS had revenue of NOK 3.2m in 2025.

Who is the general manager of OLAVS PUB AS?

Håvard Skjelstad is registered as general manager of OLAVS PUB AS.

Where is OLAVS PUB AS based?

OLAVS PUB AS has its business address in Greåker.

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.