BIZTRAC BETA
Rental and operating of own or leased real estate

TEET 1 AS

Org. no. 997466993 Limited company (AS) Lyngdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 896,000
Equity NOK 8.6m
Incorporated 2011
Share capital NOK 2.9m

Signals

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

TEET 1 AS is registered as a limited company in Lyngdal, Agder with organisation number 997466993. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 2.9m, divided into 3601 shares. The company's stated purpose is: “Eie og utleie av fast eiendom, drive handel i tilknytning til dette, delta i andre selskaper og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 896,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 896,000
Equity
NOK 8.6m
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns TEET 1 AS?

BIRK AS
TEET 1 AS
NOK 1.6m rev. · NOK 896,000 profit

TEET 1 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TEET 1 AS er morselskap for 10 datterselskaper:

Frequently asked questions about TEET 1 AS

Who owns TEET 1 AS?

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

What is the revenue of TEET 1 AS?

TEET 1 AS had revenue of NOK 1.6m in 2024.

Who is the general manager of TEET 1 AS?

Petter Birkeland is registered as general manager of TEET 1 AS.

Where is TEET 1 AS based?

TEET 1 AS has its business address in Lyngdal.

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.