BIZTRAC BETA
Rental and operating of own or leased real estate

STRYN 365 AS

Org. no. 925688592 Limited company (AS) Stryn Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 222,000
Operating profit NOK 169,000
Equity NOK 31,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STRYN 365 AS is registered as a limited company in Stryn, Vestland with organisation number 925688592. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av egen eller leid fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 222,000 in revenue and NOK 169,000 in operating profit.

Key figures · 2025

Revenue
NOK 222,000
Operating profit
NOK 169,000
Equity
NOK 31,000
Est. value
NOK 284,000

Financial health · 2025

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

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

Who owns STRYN 365 AS?

KARSTAD INVERSIÒN AS
STRYN 365 AS
NOK 222,000 rev. · NOK 169,000 profit

STRYN 365 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRYN 365 AS

Who owns STRYN 365 AS?

KARSTAD INVERSIÒN AS is the largest registered owner, with 100.0%.

What is the revenue of STRYN 365 AS?

STRYN 365 AS had revenue of NOK 222,000 in 2025.

Who is the general manager of STRYN 365 AS?

Kjetil Karstad is registered as general manager of STRYN 365 AS.

Where is STRYN 365 AS based?

STRYN 365 AS has its business address in Stryn.

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.