BIZTRAC BETA
Site preparation

PER ODD AUSTAD A/S

Org. no. 946996211 Limited company (AS) Steinkjer Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK −241,000
Equity NOK 2.7m
Incorporated 1988
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−241k kr).

PER ODD AUSTAD A/S is registered as a limited company in Steinkjer, Trøndelag with organisation number 946996211. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1988 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive virksomhet som maskinentreprenør, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK −241,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK −241,000
Equity
NOK 2.7m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns PER ODD AUSTAD A/S?

PER ERIK AUSTAD
PER ODD AUSTAD A/S
NOK 2.5m rev. · NOK −241,000 profit

PER ODD AUSTAD A/S has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about PER ODD AUSTAD A/S

Who owns PER ODD AUSTAD A/S?

PER ERIK AUSTAD is the largest registered owner, with 40.0%.

What is the revenue of PER ODD AUSTAD A/S?

PER ODD AUSTAD A/S had revenue of NOK 2.5m in 2024.

Who is the general manager of PER ODD AUSTAD A/S?

Per Erik Austad is registered as general manager of PER ODD AUSTAD A/S.

Where is PER ODD AUSTAD A/S based?

PER ODD AUSTAD A/S has its business address in Steinkjer.

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.