biztrac. BETA
COMPANY REGISTER PROFILE
997755375 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

BYGG & ENTREPRENØR PARTNER AS

Org. no. 997755375 Limited company (AS) Bergen Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −34,000
Equity NOK 2.0m
Incorporated 2011
Share capital NOK 200,000

Signals

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

BYGG & ENTREPRENØR PARTNER AS is registered as a limited company in Bergen, Vestland with organisation number 997755375. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2011. Registered share capital is NOK 200,000, divided into 300000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse. ”.

Former names: KARENSLYST ÅRGANG 2011 XLIV AS

Key figures · 2025

Operating profit
NOK −34,000
▲ +19 %
Equity
NOK 2.0m
▼ −2 %
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-1.7%
Not satisfactory
Return on total assets
Solidity
98.5%
Very good
Equity as a share of total capital

Who owns BYGG & ENTREPRENØR PARTNER AS?

BYGG & ENTREPRENØR PARTNER AS
· NOK −34,000 profit

BYGG & ENTREPRENØR PARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGG & ENTREPRENØR PARTNER AS

Who owns BYGG & ENTREPRENØR PARTNER AS?

VIKING CAPITAL AS is the largest registered owner, with 100.0%.

Where is BYGG & ENTREPRENØR PARTNER AS based?

BYGG & ENTREPRENØR PARTNER AS has its business address in Bergen.

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.