biztrac. BETA
COMPANY REGISTER PROFILE
911917017 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠AT BYGG OG VEDLIKEHOLD AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Construction of residential and non-residential buildings

AT BYGG OG VEDLIKEHOLD AS

Org. no. 911917017 Limited company (AS) Bergen Incorporated 2013 In liquidation
Operating profit NOK 0
Equity NOK 146
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

AT BYGG OG VEDLIKEHOLD AS is registered as a limited company in Bergen, Vestland with organisation number 911917017. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tømrer arbeid og vedlikehold av bygg. Eks: boder, terrasser, tilbygg og diverse.”.

Key figures · 2025

Operating profit
NOK 0
▼ −100 %
Equity
NOK 146
▲ +131 %

Financial health · 2025

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

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

Who owns AT BYGG OG VEDLIKEHOLD AS?

AT BYGG OG VEDLIKEHOLD AS
· NOK 0 profit

AT BYGG OG VEDLIKEHOLD AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about AT BYGG OG VEDLIKEHOLD AS

Who owns AT BYGG OG VEDLIKEHOLD AS?

Arve Skage is the largest registered owner, with 50.0%.

Where is AT BYGG OG VEDLIKEHOLD AS based?

AT BYGG OG VEDLIKEHOLD AS has its business address in Nesttun.

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.