BIZTRAC BETA
Buying and selling of own real estate

FIANO ERBALUCE AS

Org. no. 815294572 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −80,000
Equity NOK 272,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−80k kr).

FIANO ERBALUCE AS is registered as a limited company in Oslo, Oslo with organisation number 815294572. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp og salg av aksjer, verdipapirer og eiendom, medvirke i andre lønnsomme forretningsområde/selskaper, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −80,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −80,000
Equity
NOK 272,000
Est. value
NOK 248,000

Financial health · 2024

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.9%
Satisfactory
Equity as a share of total capital

Who owns FIANO ERBALUCE AS?

KEN ENGEBRETSEN
FIANO ERBALUCE AS
NOK 0 rev. · NOK −80,000 profit

FIANO ERBALUCE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FIANO ERBALUCE AS own?

FIANO ERBALUCE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FIANO ERBALUCE AS

Who owns FIANO ERBALUCE AS?

KEN ENGEBRETSEN is the largest registered owner, with 100.0%.

What is the revenue of FIANO ERBALUCE AS?

FIANO ERBALUCE AS had revenue of NOK 0 in 2024.

Where is FIANO ERBALUCE AS based?

FIANO ERBALUCE AS has its business address in Oslo.

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.