BIZTRAC BETA
COMPANY REGISTER PROFILE
934974778 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Freight transport by road

TEKBIT AS

Org. no. 934974778 Limited company (AS) Lillehammer Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK 6,000
Equity NOK 29,000
Incorporated 2025
Share capital NOK 30,000

TEKBIT AS is registered as a limited company in Lillehammer, Innlandet with organisation number 934974778. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen godstransport på vei - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK 6,000
Equity
NOK 29,000
Est. value
NOK 33,000

Financial health · 2025

Liquidity
21.89
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
95.4%
Weak
Equity as a share of total capital

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

Who owns TEKBIT AS?

JAKOB KRISTIAN HOLE
TEKBIT AS
NOK 16,000 rev. · NOK 6,000 profit

TEKBIT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEKBIT AS

Who owns TEKBIT AS?

JAKOB KRISTIAN HOLE is the largest registered owner, with 100.0%.

What is the revenue of TEKBIT AS?

TEKBIT AS had revenue of NOK 16,000 in 2025.

Who is the general manager of TEKBIT AS?

Jakob Kristian Hole is registered as general manager of TEKBIT AS.

Where is TEKBIT AS based?

TEKBIT AS has its business address in Lillehammer.

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.