BIZTRAC BETA
Repair and maintenance of motor vehicles

BRD. ELLEFSENS EFTF. AS

Org. no. 994705407 Limited company (AS) Risør Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 10.0m
Operating profit NOK 162,000
Equity NOK 1.1m
Incorporated 2009
Employees 7
Share capital NOK 738,000

BRD. ELLEFSENS EFTF. AS is registered as a limited company in Risør, Agder with organisation number 994705407. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2009 and has 7 registered employees. Registered share capital is NOK 738,000, divided into 7375 shares. The company's stated purpose is: “Bil- og motorverksted, salg, agenturvirksomhet og hva dermed står i forbindelse. Selskapet kan også delta i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.0m in revenue and NOK 162,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.0m
Operating profit
NOK 162,000
Equity
NOK 1.1m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns BRD. ELLEFSENS EFTF. AS?

LOKANDER EIENDOM AS
BRD. ELLEFSENS EFTF. AS
NOK 10.0m rev. · NOK 162,000 profit

BRD. ELLEFSENS EFTF. AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRD. ELLEFSENS EFTF. AS

Who owns BRD. ELLEFSENS EFTF. AS?

LOKANDER EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BRD. ELLEFSENS EFTF. AS?

BRD. ELLEFSENS EFTF. AS had revenue of NOK 10.0m in 2024.

Who is the general manager of BRD. ELLEFSENS EFTF. AS?

Atle Lokander is registered as general manager of BRD. ELLEFSENS EFTF. AS.

Where is BRD. ELLEFSENS EFTF. AS based?

BRD. ELLEFSENS EFTF. AS has its business address in Risør.

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.