BIZTRAC BETA
COMPANY REGISTER PROFILE
826693622 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Construction of residential and non-residential buildings

SKAPE BYGG NUF

Org. no. 826693622 Norwegian division of foreign business enterprise (NUF) Bærum Active
Ownership graph ↗
Revenue 2023 NOK 2.7m
Operating profit NOK 1.3m
Equity NOK 1.4m

Signals

1 flags
  • Nylig endring 2026-04-09 Konkurs registrert 2026-04-09.

SKAPE BYGG NUF is registered as a norwegian division of foreign business enterprise in Bærum, Akershus with organisation number 826693622. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The most recent filed accounts, for the 2023 financial year, show NOK 2.7m in revenue and NOK 1.3m in operating profit.

Key figures · 2023

Revenue
NOK 2.7m
Operating profit
NOK 1.3m
Equity
NOK 1.4m
Est. value
NOK 4.6m

Financial health · 2023

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
66.0%
Very good
Equity as a share of total capital

Who owns SKAPE BYGG NUF?

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

Frequently asked questions about SKAPE BYGG NUF

What is the revenue of SKAPE BYGG NUF?

SKAPE BYGG NUF had revenue of NOK 2.7m in 2023.

Where is SKAPE BYGG NUF based?

SKAPE BYGG NUF has its business address in Skui.

Property

Business address Arnesenga 4C, 1340 Skui
Cadastral unit 3201-64/82/0/0
Building Rekkehus · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.