BIZTRAC BETA
Rental and operating of own or leased real estate

TEIGEN BYGGUTVIKLING AS

Org. no. 996331423 Limited company (AS) Kvinnherad Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 33.0m
Operating profit NOK 1.6m
Equity NOK 5.8m
Incorporated 2010
Share capital NOK 258,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TEIGEN BYGGUTVIKLING AS is registered as a limited company in Kvinnherad, Vestland with organisation number 996331423. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 258,000, divided into 258216 shares. The company's stated purpose is: “Eie, forvalte og utvikle eiendom. Samt investere i eiendom og i andre selskaper, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.0m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 33.0m
Operating profit
NOK 1.6m
Equity
NOK 5.8m
Est. value
NOK 6.7m

Financial health · 2024

Liquidity
4.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.0%
Satisfactory
Equity as a share of total capital

Who owns TEIGEN BYGGUTVIKLING AS?

TEIGEN HOLDING AS
TEIGEN BYGGUTVIKLING AS
NOK 33.0m rev. · NOK 1.6m profit

TEIGEN BYGGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEIGEN BYGGUTVIKLING AS

Who owns TEIGEN BYGGUTVIKLING AS?

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

What is the revenue of TEIGEN BYGGUTVIKLING AS?

TEIGEN BYGGUTVIKLING AS had revenue of NOK 33.0m in 2024.

Where is TEIGEN BYGGUTVIKLING AS based?

TEIGEN BYGGUTVIKLING AS has its business address in Husnes.

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.