BIZTRAC BETA
Rental and operating of own or leased real estate

TEMASENTERET AS

Org. no. 935697336 Limited company (AS) Ålesund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 466,000
Operating profit NOK 4,000
Equity NOK 1.2m
Incorporated 2025
Share capital NOK 3.3m

Signals

1 flags
  • Nylig endring 2026-06-05 Aksjekapital registrert 2026-06-05.

TEMASENTERET AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 935697336. 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 3.3m, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, samt ved aksjeeie eller på annen måte å være interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 466,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 466,000
Operating profit
NOK 4,000
Equity
NOK 1.2m
Est. value
NOK 839,000

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.5%
Good
Equity as a share of total capital

Who owns TEMASENTERET AS?

TYSNES & NILSEN HOLDING AS
TEMASENTERET AS
NOK 466,000 rev. · NOK 4,000 profit

TEMASENTERET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEMASENTERET AS

Who owns TEMASENTERET AS?

TYSNES & NILSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TEMASENTERET AS?

TEMASENTERET AS had revenue of NOK 466,000 in 2025.

Who is the general manager of TEMASENTERET AS?

Knut Erik Tysnes is registered as general manager of TEMASENTERET AS.

Where is TEMASENTERET AS based?

TEMASENTERET AS has its business address in Skodje.

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.