BIZTRAC BETA
Rental and operating of own or leased real estate

RÅDHUSGATA 3 AS

Org. no. 928070018 Limited company (AS) Kragerø Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 576,000
Operating profit NOK −292,000
Equity NOK 288,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

RÅDHUSGATA 3 AS is registered as a limited company in Kragerø, Telemark with organisation number 928070018. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Handels-, investerings- og eiendomsvirksomhet, samt å delta i andre selskaper med slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 576,000 in revenue and NOK −292,000 in operating profit.

Key figures · 2024

Revenue
NOK 576,000
Operating profit
NOK −292,000
Equity
NOK 288,000
Est. value
NOK 979,000

Financial health · 2024

Liquidity
89.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.4%
Good
Equity as a share of total capital

Who owns RÅDHUSGATA 3 AS?

FREDENSBORG KRAGERØ AS
RÅDHUSGATA 3 AS
NOK 576,000 rev. · NOK −292,000 profit

RÅDHUSGATA 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RÅDHUSGATA 3 AS

Who owns RÅDHUSGATA 3 AS?

FREDENSBORG KRAGERØ AS is the largest registered owner, with 100.0%.

What is the revenue of RÅDHUSGATA 3 AS?

RÅDHUSGATA 3 AS had revenue of NOK 576,000 in 2024.

Where is RÅDHUSGATA 3 AS based?

RÅDHUSGATA 3 AS has its business address in Kragerø.

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.