biztrac. BETA
COMPANY REGISTER PROFILE
936085008 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Joinery installation

TERA BYGG AS

Org. no. 936085008 Limited company (AS) Stavanger Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −45,000
Equity NOK −15,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15k kr).

TERA BYGG AS is registered as a limited company in Stavanger, Rogaland with organisation number 936085008. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tilby tømrer, oppføring og vedlikehold av bygninger. Gulvlegging, flislegging og tapetsering. Malertjenester. Murertjenester. Snekkerarbeid, montering av dører, vinduer, kjøkken med mer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −45,000
Equity
NOK −15,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns TERA BYGG AS?

TERA BYGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TERA BYGG AS

Who owns TERA BYGG AS?

Aleksejs Jakovlevs is the largest registered owner, with 33.3%.

What is the revenue of TERA BYGG AS?

TERA BYGG AS had revenue of NOK 0 in 2025.

Who is the general manager of TERA BYGG AS?

Aleksejs Jakovlevs is registered as general manager of TERA BYGG AS.

Where is TERA BYGG AS based?

TERA BYGG AS has its business address in Hafrsfjord.

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.