biztrac. BETA
COMPANY REGISTER PROFILE
912694399 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

BANE-VEI ELEKTRO AS

Org. no. 912694399 Limited company (AS) Lillestrøm Incorporated 2013 Active
Revenue 2025 NOK 2.2m
Operating profit NOK 956,000
Equity NOK 331,000
Incorporated 2013
Share capital NOK 30,000

BANE-VEI ELEKTRO AS is registered as a limited company in Lillestrøm, Akershus with organisation number 912694399. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Elektrotekniske konsulenttjenester, eie, leie ut og ellers drifte fast eiendom, samt delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 956,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
▼ −6 %
Operating profit
NOK 956,000
▲ +13 %
Equity
NOK 331,000
▼ −20 %
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
1.85
Good
Current assets ÷ current liabilities
Profitability
107.1%
Very good
Return on total assets
Solidity
35.0%
Good
Equity as a share of total capital

Who owns BANE-VEI ELEKTRO AS?

BANE-VEI ELEKTRO AS
NOK 2.2m rev. · NOK 956,000 profit

BANE-VEI ELEKTRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BANE-VEI ELEKTRO AS

Who owns BANE-VEI ELEKTRO AS?

Bjørn Olav Aaslund is the largest registered owner, with 100.0%.

What is the revenue of BANE-VEI ELEKTRO AS?

BANE-VEI ELEKTRO AS had revenue of NOK 2.2m in 2025.

Who is the general manager of BANE-VEI ELEKTRO AS?

Bjørn Olav Aaslund is registered as general manager of BANE-VEI ELEKTRO AS.

Where is BANE-VEI ELEKTRO AS based?

BANE-VEI ELEKTRO AS has its business address in Fetsund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.