BIZTRAC BETA
Beverage serving activities

LUNDETANGEN PUB DRIFT AS

Org. no. 913953959 Limited company (AS) Skien Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 10.1m
Operating profit NOK 491,000
Equity NOK 3.2m
Incorporated 2014
Employees 15
Share capital NOK 30,000

LUNDETANGEN PUB DRIFT AS is registered as a limited company in Skien, Telemark with organisation number 913953959. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2014 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Pubdrift og virksomhet i naturlig tilknytning til dette, samt å helt eller delvis delta i eller eie andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.1m in revenue and NOK 491,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.1m
Operating profit
NOK 491,000
Equity
NOK 3.2m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns LUNDETANGEN PUB DRIFT AS?

ELIOT HOLDING AS
LUNDETANGEN PUB DRIFT AS
NOK 10.1m rev. · NOK 491,000 profit

LUNDETANGEN PUB DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUNDETANGEN PUB DRIFT AS

Who owns LUNDETANGEN PUB DRIFT AS?

ELIOT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LUNDETANGEN PUB DRIFT AS?

LUNDETANGEN PUB DRIFT AS had revenue of NOK 10.1m in 2025.

Who is the general manager of LUNDETANGEN PUB DRIFT AS?

Randi Baksaas is registered as general manager of LUNDETANGEN PUB DRIFT AS.

Where is LUNDETANGEN PUB DRIFT AS based?

LUNDETANGEN PUB DRIFT AS has its business address in Skien.

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.