biztrac. BETA
COMPANY REGISTER PROFILE
993866881 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠FAUSKE EIENDOMSUTVIKLING AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Rental and operating of own or leased real estate

FAUSKE EIENDOMSUTVIKLING AS

Org. no. 993866881 Limited company (AS) Bodø Incorporated 2009 Compulsory dissolution
Operating profit NOK −1,000
Equity NOK 14.8m
Incorporated 2009
Share capital NOK 252,000

Signals

1 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.

FAUSKE EIENDOMSUTVIKLING AS is registered as a limited company in Bodø, Nordland with organisation number 993866881. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 252,000, divided into 25164 shares. The company's stated purpose is: “Eie, utvikle og forvalte eiendommer og hva som hermed står i følge.”.

Key figures · 2023

Operating profit
NOK −1,000
▲ +100 %
Equity
NOK 14.8m
▲ +178 %

Financial health · 2023

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
30.4%
Good
Equity as a share of total capital

Who owns FAUSKE EIENDOMSUTVIKLING AS?

FAUSKE EIENDOMSUTVIKLING AS
· NOK −1,000 profit

FAUSKE EIENDOMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FAUSKE EIENDOMSUTVIKLING AS own?

FAUSKE EIENDOMSUTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FAUSKE EIENDOMSUTVIKLING AS

Who owns FAUSKE EIENDOMSUTVIKLING AS?

GREENSIDE INVEST AS is the largest registered owner, with 98.9%.

Where is FAUSKE EIENDOMSUTVIKLING AS based?

FAUSKE EIENDOMSUTVIKLING AS has its business address in Bodø.

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.