BIZTRAC BETA
Construction of residential and non-residential buildings

FEDJE UTBYGGINGSSELSKAP AS

Org. no. 988202665 Limited company (AS) Fedje Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 1.6m
Incorporated 2005
Share capital NOK 105,000

Signals

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

FEDJE UTBYGGINGSSELSKAP AS is registered as a limited company in Fedje, Vestland with organisation number 988202665. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 105,000, divided into 105 shares. The company's stated purpose is: “Stå for oppføring av boliger og andre bygg, kjøp og salg av tomter samt annen virksomhet som naturlig faller inn under dette ved aksjekjøp eller på annen måte.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 1.6m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns FEDJE UTBYGGINGSSELSKAP AS?

KASAM AS
FEDJE UTBYGGINGSSELSKAP AS
· NOK −16,000 profit

FEDJE UTBYGGINGSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FEDJE UTBYGGINGSSELSKAP AS own?

FEDJE UTBYGGINGSSELSKAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FEDJE UTBYGGINGSSELSKAP AS

Who owns FEDJE UTBYGGINGSSELSKAP AS?

KASAM AS is the largest registered owner, with 100.0%.

Where is FEDJE UTBYGGINGSSELSKAP AS based?

FEDJE UTBYGGINGSSELSKAP AS has its business address in Fedje.

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.