BIZTRAC BETA
Event catering activities

JENTAN PÅ BÅLY AS

Org. no. 888434232 Limited company (AS) Lindesnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 10.2m
Operating profit NOK 816,000
Equity NOK 5.1m
Incorporated 2005
Employees 13
Share capital NOK 200,000

JENTAN PÅ BÅLY AS is registered as a limited company in Lindesnes, Agder with organisation number 888434232. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2005 and has 13 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Delikatesseforretning, samt cateringkjøkken/virksomhet samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.2m in revenue and NOK 816,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.2m
Operating profit
NOK 816,000
Equity
NOK 5.1m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns JENTAN PÅ BÅLY AS?

LIVE UELAND
JENTAN PÅ BÅLY AS
NOK 10.2m rev. · NOK 816,000 profit

JENTAN PÅ BÅLY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JENTAN PÅ BÅLY AS

Who owns JENTAN PÅ BÅLY AS?

LIVE UELAND is the largest registered owner, with 50.0%.

What is the revenue of JENTAN PÅ BÅLY AS?

JENTAN PÅ BÅLY AS had revenue of NOK 10.2m in 2024.

Who is the general manager of JENTAN PÅ BÅLY AS?

Lene Fjeldskår is registered as general manager of JENTAN PÅ BÅLY AS.

Where is JENTAN PÅ BÅLY AS based?

JENTAN PÅ BÅLY AS has its business address in Lindesnes.

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.