BIZTRAC BETA
Construction of residential and non-residential buildings

TK BOLIG AS

Org. no. 815625862 Limited company (AS) Arendal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −21,000
Equity NOK −513,000
Incorporated 2015
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−513k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

TK BOLIG AS is registered as a limited company in Arendal, Agder with organisation number 815625862. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Oppføring av boliger og andre bygg og dertil hørende virksomhet, herunder investering i fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −21,000
Equity
NOK −513,000

Financial health · 2024

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

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

Who owns TK BOLIG AS?

KEST INVEST AS
TK BOLIG AS
NOK 0 rev. · NOK −21,000 profit

TK BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TK BOLIG AS

Who owns TK BOLIG AS?

KEST INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TK BOLIG AS?

TK BOLIG AS had revenue of NOK 0 in 2024.

Who is the general manager of TK BOLIG AS?

Trygve Eriksen is registered as general manager of TK BOLIG AS.

Where is TK BOLIG AS based?

TK BOLIG AS has its business address in Arendal.

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.