BIZTRAC BETA
Civil engineering activities

VARANGERTAKST AS

Org. no. 919626739 Limited company (AS) Vadsø Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 179,000
Operating profit NOK 1,000
Equity NOK 54,000
Incorporated 2017
Share capital NOK 30,000

VARANGERTAKST AS is registered as a limited company in Vadsø, Finnmark with organisation number 919626739. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Taksering, rådgivnings tjenester, byggeledelse, prosjekt administrasjon, prosjektering, arkitekttjenester, entreprenør virksomhet, utleie og investering i andre selskaper, og dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 179,000 in revenue and NOK 1,000 in operating profit.

Key figures · 2025

Revenue
NOK 179,000
Operating profit
NOK 1,000
Equity
NOK 54,000
Est. value
NOK 34,000

Financial health · 2025

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

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

Who owns VARANGERTAKST AS?

ROGER PEDERSEN
VARANGERTAKST AS
NOK 179,000 rev. · NOK 1,000 profit

VARANGERTAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VARANGERTAKST AS

Who owns VARANGERTAKST AS?

ROGER PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of VARANGERTAKST AS?

VARANGERTAKST AS had revenue of NOK 179,000 in 2025.

Who is the general manager of VARANGERTAKST AS?

Roger Pedersen is registered as general manager of VARANGERTAKST AS.

Where is VARANGERTAKST AS based?

VARANGERTAKST AS has its business address in Vestre Jakobselv.

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.