BIZTRAC BETA
Other technical consultancy

TEKMAS AS

Org. no. 988647969 Limited company (AS) Vestby Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 459,000
Equity NOK −804,000
Incorporated 2005
Share capital NOK 200,000

Signals

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

TEKMAS AS is registered as a limited company in Vestby, Akershus with organisation number 988647969. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Utvikling og salg av produkter til bruk i bygg- og anleggsbransjen, og investeringsvirksomhet i aksjer og andeler i andre selskaper av beslektet art innen- og utenlands, herunder også gjennom datterselskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 459,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 459,000
Equity
NOK −804,000
Est. value
NOK 2.1m

Financial health · 2025

Liquidity
4.67
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-172.7%
Weak
Equity as a share of total capital

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

Who owns TEKMAS AS?

PHYSIOTECH AS
TEKMAS AS
NOK 1.2m rev. · NOK 459,000 profit

TEKMAS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEKMAS AS

Who owns TEKMAS AS?

PHYSIOTECH AS is the largest registered owner, with 52.5%.

What is the revenue of TEKMAS AS?

TEKMAS AS had revenue of NOK 1.2m in 2025.

Who is the general manager of TEKMAS AS?

Terje Wik Mikkelsen is registered as general manager of TEKMAS AS.

Where is TEKMAS AS based?

TEKMAS AS has its business address in Son.

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.