BIZTRAC BETA
COMPANY REGISTER PROFILE
928285170 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

NORDIC PROPERTY TEAM AS

Org. no. 928285170 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 192,000
Operating profit NOK 141,000
Equity NOK 596,000
Incorporated 2021
Share capital NOK 1.0m

NORDIC PROPERTY TEAM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928285170. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 1.0m, divided into 300 shares. The company's stated purpose is: “Kjøp, utvikling, oppussing, utleie og salg av eiendommer. Primært så er det boligeiendommer, men kan delta i det meste av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 192,000 in revenue and NOK 141,000 in operating profit.

Key figures · 2025

Revenue
NOK 192,000
Operating profit
NOK 141,000
Equity
NOK 596,000
Est. value
NOK 554,000

Financial health · 2025

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

Who owns NORDIC PROPERTY TEAM AS?

KUSLU HOLDING AS
NORDIC PROPERTY TEAM AS
NOK 192,000 rev. · NOK 141,000 profit

NORDIC PROPERTY TEAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDIC PROPERTY TEAM AS

Who owns NORDIC PROPERTY TEAM AS?

KUSLU HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NORDIC PROPERTY TEAM AS?

NORDIC PROPERTY TEAM AS had revenue of NOK 192,000 in 2025.

Where is NORDIC PROPERTY TEAM AS based?

NORDIC PROPERTY TEAM AS has its business address in Saupstad.

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.