BIZTRAC BETA
COMPANY REGISTER PROFILE
931228315 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Joinery installation

VIKEN BYGG OG REHABILITERING AS

Org. no. 931228315 Limited company (AS) Frogn Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

VIKEN BYGG OG REHABILITERING AS is registered as a limited company in Frogn, Akershus with organisation number 931228315. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Snekker, tilbygg, oppussing, renovering, riving, maling.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: STORM BYGG OG REHABILITERING AS

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 31,000

Financial health · 2024

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

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

Who owns VIKEN BYGG OG REHABILITERING AS?

ABUZAR KUTAEV
VIKEN BYGG OG REHABILITERING AS
NOK 0 rev. · NOK 0 profit

VIKEN BYGG OG REHABILITERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKEN BYGG OG REHABILITERING AS

Who owns VIKEN BYGG OG REHABILITERING AS?

ABUZAR KUTAEV is the largest registered owner, with 100.0%.

What is the revenue of VIKEN BYGG OG REHABILITERING AS?

VIKEN BYGG OG REHABILITERING AS had revenue of NOK 0 in 2024.

Where is VIKEN BYGG OG REHABILITERING AS based?

VIKEN BYGG OG REHABILITERING AS has its business address in Drøbak.

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.