biztrac. BETA
COMPANY REGISTER PROFILE
931857460 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

VARJJAT TAKST AS

Org. no. 931857460 Limited company (AS) Nesseby Incorporated 2023 Active
Revenue 2025 NOK 1.6m
Operating profit NOK −359,000
Equity NOK −156,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

VARJJAT TAKST AS is registered as a limited company in Nesseby, Finnmark with organisation number 931857460. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Takstoppdrag og byggrådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −359,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▼ −31 %
Operating profit
NOK −359,000
▼ −226 %
Equity
NOK −156,000
▼ −177 %

Financial health · 2025

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-113.8%
Weak
Equity as a share of total capital

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

Who owns VARJJAT TAKST AS?

VARJJAT TAKST AS
NOK 1.6m rev. · NOK −359,000 profit

VARJJAT TAKST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VARJJAT TAKST AS

Who owns VARJJAT TAKST AS?

Svein Kandola is the largest registered owner, with 51.7%.

What is the revenue of VARJJAT TAKST AS?

VARJJAT TAKST AS had revenue of NOK 1.6m in 2025.

Who is the general manager of VARJJAT TAKST AS?

Svein Kandola is registered as general manager of VARJJAT TAKST AS.

Where is VARJJAT TAKST AS based?

VARJJAT TAKST AS has its business address in Varangerbotn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.