BIZTRAC BETA
Rental and operating of own or leased real estate

TOPP TEK BYGG AS

Org. no. 953116960 Limited company (AS) Kristiansand Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −14,000
Equity NOK 442,000
Incorporated 1989
Share capital NOK 105,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).

TOPP TEK BYGG AS is registered as a limited company in Kristiansand, Agder with organisation number 953116960. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 105,000, divided into 10500 shares. The company's stated purpose is: “Kjøp og drive næringsbygg, samt deltagelse i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 442,000
Est. value
NOK 327,000

Financial health · 2024

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

Who owns TOPP TEK BYGG AS?

OLE KRISTIAN GULBRANDSEN
TOPP TEK BYGG AS
NOK 0 rev. · NOK −14,000 profit

TOPP TEK BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPP TEK BYGG AS

Who owns TOPP TEK BYGG AS?

OLE KRISTIAN GULBRANDSEN is the largest registered owner, with 55.0%.

What is the revenue of TOPP TEK BYGG AS?

TOPP TEK BYGG AS had revenue of NOK 0 in 2024.

Who is the general manager of TOPP TEK BYGG AS?

Ole Kristian Gulbrandsen is registered as general manager of TOPP TEK BYGG AS.

Where is TOPP TEK BYGG AS based?

TOPP TEK BYGG AS has its business address in Kristiansand S.

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.