biztrac. BETA
COMPANY REGISTER PROFILE
829101122 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TK NÆRINGSUTVIKLING AS

Org. no. 829101122 Limited company (AS) Eidsvoll Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 676,000
Operating profit NOK 574,000
Equity NOK 88,000
Incorporated 2022
Share capital NOK 30,000

TK NÆRINGSUTVIKLING AS is registered as a limited company in Eidsvoll, Akershus with organisation number 829101122. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å investere i og forvalte eiendommer og hva som dermed står i forbindelse”. The most recent filed accounts, for the 2025 financial year, show NOK 676,000 in revenue and NOK 574,000 in operating profit.

Key figures · 2025

Revenue
NOK 676,000
▲ +27 %
Operating profit
NOK 574,000
▲ +27 %
Equity
NOK 88,000
▼ −63 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
5.1%
Weak
Return on total assets
Solidity
0.8%
Weak
Equity as a share of total capital

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

Who owns TK NÆRINGSUTVIKLING AS?

TK NÆRINGSUTVIKLING AS
NOK 676,000 rev. · NOK 574,000 profit

TK NÆRINGSUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TK NÆRINGSUTVIKLING AS

Who owns TK NÆRINGSUTVIKLING AS?

TK EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of TK NÆRINGSUTVIKLING AS?

TK NÆRINGSUTVIKLING AS had revenue of NOK 676,000 in 2025.

Where is TK NÆRINGSUTVIKLING AS based?

TK NÆRINGSUTVIKLING AS has its business address in Råholt.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.