BIZTRAC BETA
Intermediation service activities for specialised construction services

ISOBYGG AS

Org. no. 825149392 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −403,000
Equity NOK 586,000
Incorporated 2020
Share capital NOK 140,000

Roles

Daglig lederFrode Næss
Regnskapsfører
Revisor
Styrets lederFrode Næss
StyremedlemGeir Håvard Østtveit
StyremedlemMorten Antonsen
StyremedlemBørre Andre Hansen
StyremedlemRoy Arne Brendeløkken

Shareholders

NameStakeSharesYear
ISOBYGG VIKEN AS 7.1% 10000.000000 2025
ISOBYGG INNLANDET AS 7.1% 10000.000000 2025
ISOBYGG VEST-FINNMARK AS 7.1% 10000.000000 2025
ISOBYGG NORDLAND AS 7.1% 10000.000000 2025
ISOBYGG SOGN AS 7.1% 10000.000000 2025
ISOBYGG MØRE OG ROMSDAL AS 7.1% 10000.000000 2025
ISOBYGG KIRKENES AS 7.1% 10000.000000 2025
ISOBYGG TELEMARK-VESTFOLD AS 7.1% 10000.000000 2025
ISOBYGG HORDALAND AS 7.1% 10000.000000 2025
ISOBYGG FOSEN AS 7.1% 10000.000000 2025
ISOBYGG NAMDALEN AS 7.1% 10000.000000 2025
ISOBYGG TROMS AS 7.1% 10000.000000 2025
ISOBYGG SØR AS 7.1% 10000.000000 2025
ISOBYGG MIDT-NORGE AS 7.1% 10000.000000 2025

Holdings in other companies

CompanyStatusStakeShares
ISOBYGG FAUSKE AS Active 21.0% 21000.000000
ISOBYGG TELEMARK-VESTFOLD AS Active 21.0% 21.000000
ISOBYGG FOSEN AS Active 21.0% 21.000000
ISOBYGG SOGN AS Active 21.0% 21.000000
ISOBYGG SØR AS Active 21.0% 21.000000
ISOBYGG HALLINGDAL AS Active 21.0% 21000.000000
ISOBYGG VEST-FINNMARK AS Active 21.0% 21.000000
ISOBYGG BUSKERUD AS Active 21.0% 6300.000000
ISOBYGG NAMDALEN AS Active 21.0% 21.000000
ISOBYGG INNLANDET AS Active 21.0% 21.000000
ISOBYGG MØRE OG ROMSDAL AS Active 21.0% 21.000000
ISOBYGG HORDALAND AS Active 21.0% 42.000000
ISOBYGG TROMS AS Active 21.0% 42.000000
ISOBYGG VIKEN AS Active 21.0% 42.000000
ISOBYGG KIRKENES AS Active 21.0% 21.000000
ISOBYGG MIDT-NORGE AS Active 21.0% 21.000000

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.