BIZTRAC BETA
Development of building projects

VIKING BYGG NORGE AS

Org. no. 922887357 Limited company (AS) Gjøvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 1.6m
Equity NOK −3.9m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,9 mill kr).

VIKING BYGG NORGE AS is registered as a limited company in Gjøvik, Innlandet with organisation number 922887357. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i verdipapirer og andre selskaper, handel.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 1.6m
Equity
NOK −3.9m
Est. value
NOK 9.5m

Financial health · 2024

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

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

Who owns VIKING BYGG NORGE AS?

VLADIMIR LEBEDENKO
VIKING BYGG NORGE AS
NOK 1.9m rev. · NOK 1.6m profit

VIKING BYGG NORGE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VIKING BYGG NORGE AS own?

VIKING BYGG NORGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIKING BYGG NORGE AS

Who owns VIKING BYGG NORGE AS?

VLADIMIR LEBEDENKO is the largest registered owner, with 90.0%.

What is the revenue of VIKING BYGG NORGE AS?

VIKING BYGG NORGE AS had revenue of NOK 1.9m in 2024.

Where is VIKING BYGG NORGE AS based?

VIKING BYGG NORGE AS has its business address in Gjøvik.

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.