BIZTRAC BETA
Holiday and other short-stay accommodation

SYFTESTAD GARD AS

Org. no. 930804487 Limited company (AS) Notodden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 227,000
Equity NOK 207,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

SYFTESTAD GARD AS is registered as a limited company in Notodden, Telemark with organisation number 930804487. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tilby utleie av unike overnattingssteder, utleie av selskapslokaler, tilby lokalmat og lokale opplevelser, samt tjenester innen medieproduksjon og samarbeid i sosiale medier.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 227,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 227,000
Equity
NOK 207,000
Est. value
NOK 953,000

Financial health · 2025

Liquidity
0.65
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.9%
Satisfactory
Equity as a share of total capital

Who owns SYFTESTAD GARD AS?

LISE MARIT SYFTESTAD
SYFTESTAD GARD AS
NOK 3.1m rev. · NOK 227,000 profit

SYFTESTAD GARD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SYFTESTAD GARD AS

Who owns SYFTESTAD GARD AS?

LISE MARIT SYFTESTAD is the largest registered owner, with 50.0%.

What is the revenue of SYFTESTAD GARD AS?

SYFTESTAD GARD AS had revenue of NOK 3.1m in 2025.

Who is the general manager of SYFTESTAD GARD AS?

Marcin Litwicki is registered as general manager of SYFTESTAD GARD AS.

Where is SYFTESTAD GARD AS based?

SYFTESTAD GARD AS has its business address in Notodden.

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.