BIZTRAC BETA
Rental and operating of own or leased real estate

STAYMATE AS

Org. no. 835519252 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −90,000
Equity NOK −89,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−89k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−90k kr).

STAYMATE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 835519252. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forvaltning av boliger for utleie og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −90,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −90,000
Equity
NOK −89,000

Financial health · 2025

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

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

Who owns STAYMATE AS?

EMBRIK SKRINDO
STAYMATE AS
NOK 1.1m rev. · NOK −90,000 profit

STAYMATE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STAYMATE AS

Who owns STAYMATE AS?

EMBRIK SKRINDO is the largest registered owner, with 50.0%.

What is the revenue of STAYMATE AS?

STAYMATE AS had revenue of NOK 1.1m in 2025.

Who is the general manager of STAYMATE AS?

Embrik Skrindo is registered as general manager of STAYMATE AS.

Where is STAYMATE AS based?

STAYMATE AS has its business address in Trondheim.

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.