BIZTRAC BETA
Electrical installation

ELBYGG MIDTNORGE AS

Org. no. 825281622 Limited company (AS) Indre Fosen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −196,000
Equity NOK 31,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−196k kr).

ELBYGG MIDTNORGE AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 825281622. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “El.installasjon, serviceoppdrag og byggetjeneste.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −196,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −196,000
Equity
NOK 31,000
Est. value
NOK 637,000

Financial health · 2025

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

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

Who owns ELBYGG MIDTNORGE AS?

FRANK BJØRNAR KRABSETH
ELBYGG MIDTNORGE AS
NOK 1.8m rev. · NOK −196,000 profit

ELBYGG MIDTNORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELBYGG MIDTNORGE AS

Who owns ELBYGG MIDTNORGE AS?

FRANK BJØRNAR KRABSETH is the largest registered owner, with 100.0%.

What is the revenue of ELBYGG MIDTNORGE AS?

ELBYGG MIDTNORGE AS had revenue of NOK 1.8m in 2025.

Who is the general manager of ELBYGG MIDTNORGE AS?

Frank Bjørnar Krabseth is registered as general manager of ELBYGG MIDTNORGE AS.

Where is ELBYGG MIDTNORGE AS based?

ELBYGG MIDTNORGE AS has its business address in Leksvik.

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.