BIZTRAC BETA
Rental and operating of own or leased real estate

LANDMANNSGÅRDEN AS

Org. no. 983466494 Limited company (AS) Skien Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −100,000
Equity NOK 11.0m
Incorporated 2001
Share capital NOK 29.5m

Signals

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

LANDMANNSGÅRDEN AS is registered as a limited company in Skien, Telemark with organisation number 983466494. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 29.5m, divided into 29546 shares. The company's stated purpose is: “Kjøp, salg, utvikling, utleie og drift av fast eiendom, herunder deltakelse i selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −100,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK −100,000
Equity
NOK 11.0m
Est. value
NOK 11.0m

Financial health · 2025

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

Who owns LANDMANNSGÅRDEN AS?

SKIEN VEKST AS
LANDMANNSGÅRDEN AS
NOK 2.3m rev. · NOK −100,000 profit

LANDMANNSGÅRDEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LANDMANNSGÅRDEN AS

Who owns LANDMANNSGÅRDEN AS?

SKIEN VEKST AS is the largest registered owner, with 66.6%.

What is the revenue of LANDMANNSGÅRDEN AS?

LANDMANNSGÅRDEN AS had revenue of NOK 2.3m in 2025.

Where is LANDMANNSGÅRDEN AS based?

LANDMANNSGÅRDEN AS has its business address in Skien.

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.