BIZTRAC BETA
Construction of residential and non-residential buildings

TEKA BYGG AS

Org. no. 974341964 Limited company (AS) Bergen Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK 784,000
Equity NOK 1.1m
Incorporated 1995
Employees 6
Share capital NOK 3.5m

TEKA BYGG AS is registered as a limited company in Bergen, Vestland with organisation number 974341964. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1995 and has 6 registered employees. Registered share capital is NOK 3.5m, divided into 20 shares. The company's stated purpose is: “Kjøp, utleie og rehabilitering av fast eiendom, tømrervirksomhet og konsulentbistand i forbindelsse med dette, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK 784,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK 784,000
Equity
NOK 1.1m
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.4%
Good
Equity as a share of total capital

Who owns TEKA BYGG AS?

TEKA HOLDING AS
TEKA BYGG AS
NOK 9.9m rev. · NOK 784,000 profit

TEKA BYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TEKA BYGG AS er morselskap for 2 datterselskaper:

Frequently asked questions about TEKA BYGG AS

Who owns TEKA BYGG AS?

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

What is the revenue of TEKA BYGG AS?

TEKA BYGG AS had revenue of NOK 9.9m in 2024.

Who is the general manager of TEKA BYGG AS?

Trond-Einar Hermansen is registered as general manager of TEKA BYGG AS.

Where is TEKA BYGG AS based?

TEKA BYGG AS has its business address in Blomsterdalen.

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.