biztrac. BETA
COMPANY REGISTER PROFILE
934551001 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Combined facilities support activities

EIKELAND BYGGSERVICE AS

Org. no. 934551001 Limited company (AS) Larvik Incorporated 2024 Active
Revenue 2025 NOK 327,000
Operating profit NOK 37,000
Equity NOK 111,000
Incorporated 2024
Share capital NOK 30,000

EIKELAND BYGGSERVICE AS is registered as a limited company in Larvik, Vestfold with organisation number 934551001. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Utføre oppdrag for håndverkere og privatkunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 327,000 in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 327,000
▲ +246 %
Operating profit
NOK 37,000
▼ −43 %
Equity
NOK 111,000
▲ +35 %
Est. value
NOK 242,000

Financial health · 2025

Liquidity
2.29
Very good
Current assets ÷ current liabilities
Profitability
29.0%
Very good
Return on total assets
Solidity
74.6%
Very good
Equity as a share of total capital

Who owns EIKELAND BYGGSERVICE AS?

EIKELAND BYGGSERVICE AS
NOK 327,000 rev. · NOK 37,000 profit

EIKELAND BYGGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKELAND BYGGSERVICE AS

Who owns EIKELAND BYGGSERVICE AS?

Peder Eikeland is the largest registered owner, with 100.0%.

What is the revenue of EIKELAND BYGGSERVICE AS?

EIKELAND BYGGSERVICE AS had revenue of NOK 327,000 in 2025.

Who is the general manager of EIKELAND BYGGSERVICE AS?

Peder Eikeland is registered as general manager of EIKELAND BYGGSERVICE AS.

Where is EIKELAND BYGGSERVICE AS based?

EIKELAND BYGGSERVICE AS has its business address in Larvik.

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.