BIZTRAC BETA
Floor and wall covering

TEKNISK GULV AS

Org. no. 925103713 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK −251,000
Equity NOK 225,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

TEKNISK GULV AS is registered as a limited company in Asker, Akershus with organisation number 925103713. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive med gulvlegging og andre håndverkstjenester, samt annen aktivitet som naturlig faller sammen med dette herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK −251,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK −251,000
Equity
NOK 225,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.9%
Weak
Equity as a share of total capital

Who owns TEKNISK GULV AS?

JAKUB MAREK CZAPLINSKI
TEKNISK GULV AS
NOK 5.3m rev. · NOK −251,000 profit

TEKNISK GULV AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TEKNISK GULV AS

Who owns TEKNISK GULV AS?

JAKUB MAREK CZAPLINSKI is the largest registered owner, with 50.0%.

What is the revenue of TEKNISK GULV AS?

TEKNISK GULV AS had revenue of NOK 5.3m in 2024.

Who is the general manager of TEKNISK GULV AS?

Fabian Sebastian Tyliba is registered as general manager of TEKNISK GULV AS.

Where is TEKNISK GULV AS based?

TEKNISK GULV AS has its business address in Slemmestad.

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.