BIZTRAC BETA
Construction of residential and non-residential buildings

CLASSIC BYGG AS

Org. no. 917316538 Limited company (AS) Aurskog-Høland Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 21,000
Equity NOK −105,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

CLASSIC BYGG AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 917316538. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av byggetjenester, prosjekteringstjenester og import og salg av byggevarer, samt andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 21,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 21,000
Equity
NOK −105,000
Est. value
NOK 104,000

Financial health · 2024

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

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

Who owns CLASSIC BYGG AS?

No shareholders are registered for CLASSIC BYGG AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about CLASSIC BYGG AS

What is the revenue of CLASSIC BYGG AS?

CLASSIC BYGG AS had revenue of NOK 1.1m in 2024.

Who is the general manager of CLASSIC BYGG AS?

Laimonas Nalivaiko is registered as general manager of CLASSIC BYGG AS.

Where is CLASSIC BYGG AS based?

CLASSIC BYGG AS has its business address in Bjørkelangen.

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.