BIZTRAC BETA
Construction of residential and non-residential buildings

ROGNSTAD BYGGTEKNIKK AS

Org. no. 913139763 Limited company (AS) Ullensaker Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 1.2m
Equity NOK 2.3m
Incorporated 2014
Share capital NOK 100,000

ROGNSTAD BYGGTEKNIKK AS is registered as a limited company in Ullensaker, Akershus with organisation number 913139763. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygninger, rehabilitering og vedlikehold av bygninger og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 1.2m
Equity
NOK 2.3m
Est. value
NOK 4.5m

Financial health · 2024

Liquidity
1.80
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.4%
Very good
Equity as a share of total capital

Who owns ROGNSTAD BYGGTEKNIKK AS?

PER ERIK ROGNSTAD
ROGNSTAD BYGGTEKNIKK AS
NOK 6.6m rev. · NOK 1.2m profit

ROGNSTAD BYGGTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROGNSTAD BYGGTEKNIKK AS

Who owns ROGNSTAD BYGGTEKNIKK AS?

PER ERIK ROGNSTAD is the largest registered owner, with 100.0%.

What is the revenue of ROGNSTAD BYGGTEKNIKK AS?

ROGNSTAD BYGGTEKNIKK AS had revenue of NOK 6.6m in 2024.

Who is the general manager of ROGNSTAD BYGGTEKNIKK AS?

Per Erik Rognstad is registered as general manager of ROGNSTAD BYGGTEKNIKK AS.

Where is ROGNSTAD BYGGTEKNIKK AS based?

ROGNSTAD BYGGTEKNIKK AS has its business address in Jessheim.

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.