BIZTRAC BETA
Other technical consultancy

EL-TILSYNET AS

Org. no. 963679890 Limited company (AS) Bærum Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 31.3m
Operating profit NOK 451,000
Equity NOK 4.9m
Incorporated 1991
Employees 32
Share capital NOK 1.0m

EL-TILSYNET AS is registered as a limited company in Bærum, Akershus with organisation number 963679890. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1991 and has 32 registered employees. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Utføre tilsynstjenester basert på de krav som til enhver tid fastsettes av myndigheter og selskapets kunder, samt tilby rådgivningstjenester basert på selskapets kompetanse innenfor de til enhver tid gjeldende habilitetsregler fra DSB.”. The most recent filed accounts, for the 2024 financial year, show NOK 31.3m in revenue and NOK 451,000 in operating profit.

Key figures · 2024

Revenue
NOK 31.3m
Operating profit
NOK 451,000
Equity
NOK 4.9m
Est. value
NOK 4.6m

Financial health · 2024

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.6%
Good
Equity as a share of total capital

Who owns EL-TILSYNET AS?

TOM MAURSTAD HOLDING AS
EL-TILSYNET AS
NOK 31.3m rev. · NOK 451,000 profit

EL-TILSYNET AS has 18 registered shareholders:

All shareholders and roles →

Frequently asked questions about EL-TILSYNET AS

Who owns EL-TILSYNET AS?

TOM MAURSTAD HOLDING AS is the largest registered owner, with 33.4%.

What is the revenue of EL-TILSYNET AS?

EL-TILSYNET AS had revenue of NOK 31.3m in 2024.

Who is the general manager of EL-TILSYNET AS?

Tom Maurstad is registered as general manager of EL-TILSYNET AS.

Where is EL-TILSYNET AS based?

EL-TILSYNET AS has its business address in Vøyenenga.

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.