BIZTRAC BETA
Beverage serving activities

DICKENS PUB AS

Org. no. 914737397 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 11.8m
Operating profit NOK 195,000
Equity NOK 746,000
Incorporated 2014
Employees 17
Share capital NOK 250,000

DICKENS PUB AS is registered as a limited company in Drammen, Buskerud with organisation number 914737397. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2014 and has 17 registered employees. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Catering, pub- og restaurantdrift samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.8m in revenue and NOK 195,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.8m
Operating profit
NOK 195,000
Equity
NOK 746,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.8%
Good
Equity as a share of total capital

Who owns DICKENS PUB AS?

FJERDINGSTAD HOLDING AS
DICKENS PUB AS
NOK 11.8m rev. · NOK 195,000 profit

DICKENS PUB AS has 3 registered shareholders:

All shareholders and roles →

Which companies does DICKENS PUB AS own?

DICKENS PUB AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DICKENS PUB AS

Who owns DICKENS PUB AS?

FJERDINGSTAD HOLDING AS is the largest registered owner, with 33.6%.

What is the revenue of DICKENS PUB AS?

DICKENS PUB AS had revenue of NOK 11.8m in 2024.

Who is the general manager of DICKENS PUB AS?

Petter Henning Thorsbye Arnebrott is registered as general manager of DICKENS PUB AS.

Where is DICKENS PUB AS based?

DICKENS PUB AS has its business address in Drammen.

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.