BIZTRAC BETA
COMPANY REGISTER PROFILE
925531588 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Civil engineering activities

BYGGESØKNAD OSLO AS

Org. no. 925531588 Limited company (AS) Skien Incorporated 2020 Active
Ownership graph ↗
Equity NOK 0
Incorporated 2020
Share capital NOK 30,000

BYGGESØKNAD OSLO AS is registered as a limited company in Skien, Telemark with organisation number 925531588. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulent og søknadstjenester ifm. byggesaker.”.

Key figures · 2025

Equity
NOK 0

Financial health · 2025

Liquidity
Not available
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 BYGGESØKNAD OSLO AS?

BYGGESØKNAD OSLO AS

BYGGESØKNAD OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGESØKNAD OSLO AS

Who owns BYGGESØKNAD OSLO AS?

NIELVE AS is the largest registered owner, with 100.0%.

Who is the general manager of BYGGESØKNAD OSLO AS?

Pål Mathisen is registered as general manager of BYGGESØKNAD OSLO AS.

Where is BYGGESØKNAD OSLO AS based?

BYGGESØKNAD OSLO AS has its business address in Skien.

Property

Business address Nedre Åsen 19, 3731 Skien
Cadastral unit 4003-213/185/0/0
Building Enebolig · 1 unit

13 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.