BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

L.EKEBERG AS

Org. no. 918072756 Limited company (AS) Kristiansand Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 46.8m
Operating profit NOK 471,000
Equity NOK 761,000
Incorporated 2016
Employees 9
Share capital NOK 500,000

L.EKEBERG AS is registered as a limited company in Kristiansand, Agder with organisation number 918072756. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2016 and has 9 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av daligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 46.8m in revenue and NOK 471,000 in operating profit.

Key figures · 2025

Revenue
NOK 46.8m
Operating profit
NOK 471,000
Equity
NOK 761,000
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.9%
Satisfactory
Equity as a share of total capital

Who owns L.EKEBERG AS?

LARS EKEBERG
L.EKEBERG AS
NOK 46.8m rev. · NOK 471,000 profit

L.EKEBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about L.EKEBERG AS

Who owns L.EKEBERG AS?

LARS EKEBERG is the largest registered owner, with 100.0%.

What is the revenue of L.EKEBERG AS?

L.EKEBERG AS had revenue of NOK 46.8m in 2025.

Who is the general manager of L.EKEBERG AS?

Lars Ekeberg is registered as general manager of L.EKEBERG AS.

Where is L.EKEBERG AS based?

L.EKEBERG AS has its business address in Kristiansand S.

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.