BIZTRAC BETA
Uoppgitt

REKOL PROSJEKT 6 AS

Org. no. 935473918 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

REKOL PROSJEKT 6 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935473918. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i og utvikling av eiendom, samt alt som hermed står i forbindelse, herunder deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 20,000
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns REKOL PROSJEKT 6 AS?

REKOL EIENDOM AS
REKOL PROSJEKT 6 AS
NOK 0 rev. · NOK −10,000 profit

REKOL PROSJEKT 6 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REKOL PROSJEKT 6 AS

Who owns REKOL PROSJEKT 6 AS?

REKOL EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of REKOL PROSJEKT 6 AS?

REKOL PROSJEKT 6 AS had revenue of NOK 0 in 2025.

Where is REKOL PROSJEKT 6 AS based?

REKOL PROSJEKT 6 AS has its business address in Trondheim.

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.