BIZTRAC BETA
Repair and maintenance of machinery

JUBS BYGG OG INDUSTRI AS

Org. no. 918991379 Limited company (AS) Frosta Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 85,000
Equity NOK 281,000
Incorporated 2017
Share capital NOK 45,000

JUBS BYGG OG INDUSTRI AS is registered as a limited company in Frosta, Trøndelag with organisation number 918991379. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2017. Registered share capital is NOK 45,000, divided into 1000 shares. The company's stated purpose is: “Utleie av arbeidskraft og maskiner, og det som naturlig følger med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 85,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 85,000
Equity
NOK 281,000
Est. value
NOK 411,000

Financial health · 2024

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

Who owns JUBS BYGG OG INDUSTRI AS?

TOR MAGNUS LUND JUBERG
JUBS BYGG OG INDUSTRI AS
NOK 1.4m rev. · NOK 85,000 profit

JUBS BYGG OG INDUSTRI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JUBS BYGG OG INDUSTRI AS

Who owns JUBS BYGG OG INDUSTRI AS?

TOR MAGNUS LUND JUBERG is the largest registered owner, with 100.0%.

What is the revenue of JUBS BYGG OG INDUSTRI AS?

JUBS BYGG OG INDUSTRI AS had revenue of NOK 1.4m in 2024.

Who is the general manager of JUBS BYGG OG INDUSTRI AS?

Tor Magnus Lund Juberg is registered as general manager of JUBS BYGG OG INDUSTRI AS.

Where is JUBS BYGG OG INDUSTRI AS based?

JUBS BYGG OG INDUSTRI AS has its business address in Frosta.

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.