BIZTRAC BETA
Construction of residential and non-residential buildings

ASK BYGG ENTREPRENØR AS

Org. no. 934231325 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 67,000
Equity NOK 82,000
Incorporated 2024
Share capital NOK 30,000

ASK BYGG ENTREPRENØR AS is registered as a limited company in Asker, Akershus with organisation number 934231325. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Entreprenør og prosjektledelse innen bygg og anlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 67,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 67,000
Equity
NOK 82,000
Est. value
NOK 264,000

Financial health · 2024

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

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

Who owns ASK BYGG ENTREPRENØR AS?

NIJO HOLDING AS
ASK BYGG ENTREPRENØR AS
NOK 1.8m rev. · NOK 67,000 profit

ASK BYGG ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASK BYGG ENTREPRENØR AS

Who owns ASK BYGG ENTREPRENØR AS?

NIJO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ASK BYGG ENTREPRENØR AS?

ASK BYGG ENTREPRENØR AS had revenue of NOK 1.8m in 2024.

Who is the general manager of ASK BYGG ENTREPRENØR AS?

Marius Rognes Johansen is registered as general manager of ASK BYGG ENTREPRENØR AS.

Where is ASK BYGG ENTREPRENØR AS based?

ASK BYGG ENTREPRENØR AS has its business address in Asker.

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.