BIZTRAC BETA
COMPANY REGISTER PROFILE
929315014 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Bankrupt UPDATED 02.09.2026
PATELA DRIFT AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Electrical installation

PATELA DRIFT AS

Org. no. 929315014 Limited company (AS) Ullensaker Incorporated 2022 Bankrupt
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 58,000
Equity NOK 72,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.

PATELA DRIFT AS is registered as a limited company in Ullensaker, Akershus with organisation number 929315014. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive med telekommunikasjon, installasjon av telekommunikasjons materiell, utvikling av programvarer og tilby it-tjenester, samt annet som faller i naturlig tilknytning.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 58,000 in operating profit.

Former names: MIKI AS

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 58,000
Equity
NOK 72,000

Financial health · 2024

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

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

Who owns PATELA DRIFT AS?

No shareholders are registered for PATELA DRIFT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about PATELA DRIFT AS

What is the revenue of PATELA DRIFT AS?

PATELA DRIFT AS had revenue of NOK 1.4m in 2024.

Where is PATELA DRIFT AS based?

PATELA DRIFT AS has its business address in Jessheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.