BIZTRAC BETA
Other real estate activities on a fee or contract basis

TAKST & BYGNINGSVERN AS

Org. no. 925942138 Limited company (AS) Nissedal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 106,000
Operating profit NOK 29,000
Equity NOK 35,000
Incorporated 2020
Share capital NOK 30,000

TAKST & BYGNINGSVERN AS is registered as a limited company in Nissedal, Telemark with organisation number 925942138. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Takst- og byggevirksomhet, rådgivning og eiendomsutvikling og andre tjenester som naturlig hører sammen med dette herunder å delta i andres selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 106,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2024

Revenue
NOK 106,000
Operating profit
NOK 29,000
Equity
NOK 35,000
Est. value
NOK 100,000

Financial health · 2024

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.4%
Weak
Equity as a share of total capital

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

Who owns TAKST & BYGNINGSVERN AS?

BENT OVE SCHJØRLIEN
TAKST & BYGNINGSVERN AS
NOK 106,000 rev. · NOK 29,000 profit

TAKST & BYGNINGSVERN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TAKST & BYGNINGSVERN AS

Who owns TAKST & BYGNINGSVERN AS?

BENT OVE SCHJØRLIEN is the largest registered owner, with 100.0%.

What is the revenue of TAKST & BYGNINGSVERN AS?

TAKST & BYGNINGSVERN AS had revenue of NOK 106,000 in 2024.

Where is TAKST & BYGNINGSVERN AS based?

TAKST & BYGNINGSVERN AS has its business address in Treungen.

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.