BIZTRAC BETA
Rental and operating of own or leased real estate

FREDNESØYA 11 AS

Org. no. 891396872 Limited company (AS) Porsgrunn Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 115,000
Operating profit NOK −53,000
Equity NOK −722,000
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−722k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−53k kr).

FREDNESØYA 11 AS is registered as a limited company in Porsgrunn, Telemark with organisation number 891396872. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 115,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2024

Revenue
NOK 115,000
Operating profit
NOK −53,000
Equity
NOK −722,000

Financial health · 2024

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

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

Who owns FREDNESØYA 11 AS?

FREDNES III UTBYGGING AS
FREDNESØYA 11 AS
NOK 115,000 rev. · NOK −53,000 profit

FREDNESØYA 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FREDNESØYA 11 AS

Who owns FREDNESØYA 11 AS?

FREDNES III UTBYGGING AS is the largest registered owner, with 100.0%.

What is the revenue of FREDNESØYA 11 AS?

FREDNESØYA 11 AS had revenue of NOK 115,000 in 2024.

Where is FREDNESØYA 11 AS based?

FREDNESØYA 11 AS has its business address in Porsgrunn.

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.