BIZTRAC BETA
Rental and operating of own or leased real estate

TEKTA EIENDOM AS

Org. no. 928139492 Limited company (AS) Modum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 620,000
Equity NOK 2.5m
Incorporated 2021
Share capital NOK 90,000

TEKTA EIENDOM AS is registered as a limited company in Modum, Buskerud with organisation number 928139492. 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 90,000, divided into 30000 shares. The company's stated purpose is: “Eie, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 620,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 620,000
Equity
NOK 2.5m
Est. value
NOK 2.6m

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.1%
Satisfactory
Equity as a share of total capital

Who owns TEKTA EIENDOM AS?

TEKTA HOLDING AS
TEKTA EIENDOM AS
NOK 1.1m rev. · NOK 620,000 profit

TEKTA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TEKTA EIENDOM AS er morselskap for 3 datterselskaper:

Frequently asked questions about TEKTA EIENDOM AS

Who owns TEKTA EIENDOM AS?

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

What is the revenue of TEKTA EIENDOM AS?

TEKTA EIENDOM AS had revenue of NOK 1.1m in 2024.

Who is the general manager of TEKTA EIENDOM AS?

Thomas Tandberg is registered as general manager of TEKTA EIENDOM AS.

Where is TEKTA EIENDOM AS based?

TEKTA EIENDOM AS has its business address in Vikersund.

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.