biztrac. BETA
COMPANY REGISTER PROFILE
914871824 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Site preparation

VE ENTREPRENØR AS

Org. no. 914871824 Limited company (AS) Bykle Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 13.4m
Operating profit NOK 461,000
Equity NOK 2.0m
Incorporated 2014
Employees 23
Share capital NOK 30,000

VE ENTREPRENØR AS is registered as a limited company in Bykle, Agder with organisation number 914871824. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014 and has 23 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet og vedlikeholdsarbeid samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.4m in revenue and NOK 461,000 in operating profit.

Former names: BYKLE VIKARPARTNER AS

Key figures · 2025

Revenue
NOK 13.4m
▼ −9 %
Operating profit
NOK 461,000
▼ −20 %
Equity
NOK 2.0m
▼ −3 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
7.1%
Satisfactory
Return on total assets
Solidity
33.5%
Good
Equity as a share of total capital

Who owns VE ENTREPRENØR AS?

VE ENTREPRENØR AS
NOK 13.4m rev. · NOK 461,000 profit

VE ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VE ENTREPRENØR AS

Who owns VE ENTREPRENØR AS?

ISOKITT NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of VE ENTREPRENØR AS?

VE ENTREPRENØR AS had revenue of NOK 13.4m in 2025.

Who is the general manager of VE ENTREPRENØR AS?

Kjell Ole Homme is registered as general manager of VE ENTREPRENØR AS.

Where is VE ENTREPRENØR AS based?

VE ENTREPRENØR AS has its business address in Bykle.

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.