BIZTRAC BETA
Construction of residential and non-residential buildings

TVEITA BYGG AS

Org. no. 927033097 Limited company (AS) Klepp Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 15.9m
Operating profit NOK 2.3m
Equity NOK 3.8m
Incorporated 2021
Employees 5
Share capital NOK 30,000

TVEITA BYGG AS is registered as a limited company in Klepp, Rogaland with organisation number 927033097. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømmermannstjenester og hva hermed står i forbindelse, herunder delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.9m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 15.9m
Operating profit
NOK 2.3m
Equity
NOK 3.8m
Est. value
NOK 8.6m

Financial health · 2025

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

Who owns TVEITA BYGG AS?

ALMA AS
TVEITA BYGG AS
NOK 15.9m rev. · NOK 2.3m profit

TVEITA BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TVEITA BYGG AS own?

TVEITA BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TVEITA BYGG AS

Who owns TVEITA BYGG AS?

ALMA AS is the largest registered owner, with 100.0%.

What is the revenue of TVEITA BYGG AS?

TVEITA BYGG AS had revenue of NOK 15.9m in 2024.

Who is the general manager of TVEITA BYGG AS?

Albert Tveita is registered as general manager of TVEITA BYGG AS.

Where is TVEITA BYGG AS based?

TVEITA BYGG AS has its business address in Kleppe.

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.