BIZTRAC BETA
Rental and operating of own or leased real estate

POSTHUSGÅRDEN AS

Org. no. 985276080 Limited company (AS) Kragerø Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 120,000
Operating profit NOK −284,000
Equity NOK 1.0m
Incorporated 2002
Share capital NOK 200,000

Signals

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

POSTHUSGÅRDEN AS is registered as a limited company in Kragerø, Telemark with organisation number 985276080. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 100 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 120,000 in revenue and NOK −284,000 in operating profit.

Key figures · 2024

Revenue
NOK 120,000
Operating profit
NOK −284,000
Equity
NOK 1.0m
Est. value
NOK 937,000

Financial health · 2024

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

Who owns POSTHUSGÅRDEN AS?

FREDENSBORG 11 AS
POSTHUSGÅRDEN AS
NOK 120,000 rev. · NOK −284,000 profit

POSTHUSGÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POSTHUSGÅRDEN AS

Who owns POSTHUSGÅRDEN AS?

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

What is the revenue of POSTHUSGÅRDEN AS?

POSTHUSGÅRDEN AS had revenue of NOK 120,000 in 2024.

Where is POSTHUSGÅRDEN AS based?

POSTHUSGÅRDEN 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.