BIZTRAC BETA
Combined facilities support activities

EIKER BOLIGSERVICE AS

Org. no. 913915909 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 474,000
Equity NOK 2.5m
Incorporated 2014
Share capital NOK 100,000

EIKER BOLIGSERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 913915909. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vaktmester- og håndverkstjenester, kjøp og salg av fast eiendom, investering i andre selskaper, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 474,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 474,000
Equity
NOK 2.5m
Est. value
NOK 3.2m

Financial health · 2024

Liquidity
6.85
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
86.8%
Very good
Equity as a share of total capital

Who owns EIKER BOLIGSERVICE AS?

ØYVIND STÆRKEBYE
EIKER BOLIGSERVICE AS
NOK 1.6m rev. · NOK 474,000 profit

EIKER BOLIGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKER BOLIGSERVICE AS

Who owns EIKER BOLIGSERVICE AS?

ØYVIND STÆRKEBYE is the largest registered owner, with 100.0%.

What is the revenue of EIKER BOLIGSERVICE AS?

EIKER BOLIGSERVICE AS had revenue of NOK 1.6m in 2024.

Who is the general manager of EIKER BOLIGSERVICE AS?

Øyvind Stærkebye is registered as general manager of EIKER BOLIGSERVICE AS.

Where is EIKER BOLIGSERVICE AS based?

EIKER BOLIGSERVICE AS has its business address in Mjøndalen.

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.