BIZTRAC BETA
Civil engineering activities

VIKA BYGG & ANLEGG AS

Org. no. 998333067 Limited company (AS) Enebakk Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −205,000
Equity NOK 138,000
Incorporated 2012
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−205k kr).

VIKA BYGG & ANLEGG AS is registered as a limited company in Enebakk, Akershus with organisation number 998333067. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Utvikling, prosjektering, utføring, import eksport alt innen bygg anlegg og ventilasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −205,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −205,000
Equity
NOK 138,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.82
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.7%
Very good
Equity as a share of total capital

Who owns VIKA BYGG & ANLEGG AS?

SID ISA RAZAVEY
VIKA BYGG & ANLEGG AS
NOK 1.3m rev. · NOK −205,000 profit

VIKA BYGG & ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKA BYGG & ANLEGG AS

Who owns VIKA BYGG & ANLEGG AS?

SID ISA RAZAVEY is the largest registered owner, with 100.0%.

What is the revenue of VIKA BYGG & ANLEGG AS?

VIKA BYGG & ANLEGG AS had revenue of NOK 1.3m in 2025.

Who is the general manager of VIKA BYGG & ANLEGG AS?

Sid Isa Razavey is registered as general manager of VIKA BYGG & ANLEGG AS.

Where is VIKA BYGG & ANLEGG AS based?

VIKA BYGG & ANLEGG AS has its business address in Ytre Enebakk.

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.