biztrac. BETA
COMPANY REGISTER PROFILE
923032649 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TRØNGSLA 4 AS

Org. no. 923032649 Limited company (AS) Flekkefjord Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 897,000
Operating profit NOK 508,000
Equity NOK 1.2m
Incorporated 2019
Share capital NOK 1.2m

TRØNGSLA 4 AS is registered as a limited company in Flekkefjord, Agder with organisation number 923032649. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 1.2m, divided into 1000 shares. The company's stated purpose is: “Utvikling og utleie av eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 897,000 in revenue and NOK 508,000 in operating profit.

Key figures · 2025

Revenue
NOK 897,000
▲ +5 %
Operating profit
NOK 508,000
▲ +18 %
Equity
NOK 1.2m
▲ +12 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
18.36
Very good
Current assets ÷ current liabilities
Profitability
7.4%
Satisfactory
Return on total assets
Solidity
17.3%
Satisfactory
Equity as a share of total capital

Who owns TRØNGSLA 4 AS?

TRØNGSLA 4 AS
NOK 897,000 rev. · NOK 508,000 profit

TRØNGSLA 4 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRØNGSLA 4 AS

Who owns TRØNGSLA 4 AS?

EGENES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TRØNGSLA 4 AS?

TRØNGSLA 4 AS had revenue of NOK 897,000 in 2025.

Where is TRØNGSLA 4 AS based?

TRØNGSLA 4 AS has its business address in Flekkefjord.

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.