BIZTRAC BETA
FS TEAM BYGG OG EIENDOM AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Development of building projects

FS TEAM BYGG OG EIENDOM AS

Org. no. 930071161 Limited company (AS) Lørenskog Incorporated 2022 Bankrupt
Ownership graph ↗
Operating profit NOK −725,000
Equity NOK −233,000
Incorporated 2022
Share capital NOK 500,000

Signals

4 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−233k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−725k kr).
  • Nylig endring 2026-07-23 Konkurs registrert 2026-07-23.

FS TEAM BYGG OG EIENDOM AS is registered as a limited company in Lørenskog, Akershus with organisation number 930071161. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av tomter og eiendom, samt utvikling av eiendommer.”.

Key figures · 2024

Operating profit
NOK −725,000
Equity
NOK −233,000

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3652.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FS TEAM BYGG OG EIENDOM AS?

No shareholders are registered for FS TEAM BYGG OG EIENDOM AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FS TEAM BYGG OG EIENDOM AS

Who is the general manager of FS TEAM BYGG OG EIENDOM AS?

Aleksandrs Ribakovs is registered as general manager of FS TEAM BYGG OG EIENDOM AS.

Where is FS TEAM BYGG OG EIENDOM AS based?

FS TEAM BYGG OG EIENDOM AS has its business address in Lørenskog.

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.