biztrac. BETA
COMPANY REGISTER PROFILE
990391858 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BYGGKJEDEN EIENDOM AS

Org. no. 990391858 Limited company (AS) Karmøy Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 115,000
Incorporated 2006
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BYGGKJEDEN EIENDOM AS is registered as a limited company in Karmøy, Rogaland with organisation number 990391858. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2006. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp/salg av fast eiendom, utleie av fast eiendom samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomher.”.

Former names: ETA EIENDOM AS

Key figures · 2025

Operating profit
NOK −11,000
▲ +6 %
Equity
NOK 115,000
▼ −9 %
Est. value
NOK 105,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
4.5%
Weak
Equity as a share of total capital

Who owns BYGGKJEDEN EIENDOM AS?

BYGGKJEDEN EIENDOM AS
· NOK −11,000 profit

BYGGKJEDEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BYGGKJEDEN EIENDOM AS er morselskap for 8 datterselskaper:

Frequently asked questions about BYGGKJEDEN EIENDOM AS

Who owns BYGGKJEDEN EIENDOM AS?

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

Where is BYGGKJEDEN EIENDOM AS based?

BYGGKJEDEN EIENDOM AS has its business address in Kopervik.

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.