BIZTRAC BETA
Rental and operating of own or leased real estate

TRK ADVISORY AS

Org. no. 989282700 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 158,000
Operating profit NOK −134,000
Equity NOK 2.7m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−134k kr).

TRK ADVISORY AS is registered as a limited company in Oslo, Oslo with organisation number 989282700. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Konsulentbistand, handel, investering i fast eiendom og verdipapirer samt annen virksomhet i tilknytning til dette, herunder deltagelse i andre selskaper med tilsvarende virksomhet gjennom egenkapital, lån eller ved avgivelse av garantier.”. The most recent filed accounts, for the 2024 financial year, show NOK 158,000 in revenue and NOK −134,000 in operating profit.

Key figures · 2024

Revenue
NOK 158,000
Operating profit
NOK −134,000
Equity
NOK 2.7m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns TRK ADVISORY AS?

TROND RIIBER KNUDSEN
TRK ADVISORY AS
NOK 158,000 rev. · NOK −134,000 profit

TRK ADVISORY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRK ADVISORY AS

Who owns TRK ADVISORY AS?

TROND RIIBER KNUDSEN is the largest registered owner, with 100.0%.

What is the revenue of TRK ADVISORY AS?

TRK ADVISORY AS had revenue of NOK 158,000 in 2024.

Where is TRK ADVISORY AS based?

TRK ADVISORY AS has its business address in Oslo.

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.