BIZTRAC BETA
Rental and operating of own or leased real estate

FT BORON AS

Org. no. 994491466 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 345,000
Operating profit NOK −667,000
Equity NOK −2.5m
Incorporated 2009
Share capital NOK 5.3m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−667k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FT BORON AS is registered as a limited company in Oslo, Oslo with organisation number 994491466. 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 5.3m, divided into 100 shares. The company's stated purpose is: “Eie eiendom og selskapsandeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 345,000 in revenue and NOK −667,000 in operating profit.

Key figures · 2025

Revenue
NOK 345,000
Operating profit
NOK −667,000
Equity
NOK −2.5m

Financial health · 2025

Liquidity
42.18
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-15.8%
Weak
Equity as a share of total capital

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

Who owns FT BORON AS?

CHRISTIANIA SECURITIES AS
FT BORON AS
NOK 345,000 rev. · NOK −667,000 profit

FT BORON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FT BORON AS

Who owns FT BORON AS?

CHRISTIANIA SECURITIES AS is the largest registered owner, with 100.0%.

What is the revenue of FT BORON AS?

FT BORON AS had revenue of NOK 345,000 in 2025.

Where is FT BORON AS based?

FT BORON 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.