BIZTRAC BETA
Construction of residential and non-residential buildings

SENJABYGG AS

Org. no. 940051398 Limited company (AS) Senja Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK 659,000
Equity NOK 919,000
Incorporated 1986
Share capital NOK 500,000

SENJABYGG AS is registered as a limited company in Senja, Troms with organisation number 940051398. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1986. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Salg av byggevarer og entreprenørtjenester, samt hva hermed følger med. Selskapet vil også delta i andre selskaper der det er hensiktsmessig.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK 659,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK 659,000
Equity
NOK 919,000
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns SENJABYGG AS?

SENJA HOLDING AS
SENJABYGG AS
NOK 8.4m rev. · NOK 659,000 profit

SENJABYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SENJABYGG AS own?

SENJABYGG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SENJABYGG AS

Who owns SENJABYGG AS?

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

What is the revenue of SENJABYGG AS?

SENJABYGG AS had revenue of NOK 8.4m in 2024.

Who is the general manager of SENJABYGG AS?

Ove Magnar Nygård is registered as general manager of SENJABYGG AS.

Where is SENJABYGG AS based?

SENJABYGG AS has its business address in Kaldfarnes.

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.