BIZTRAC BETA
Raising of animals n.e.c.

BIINNTEKT AS

Org. no. 922809267 Limited company (AS) Kongsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 15,000
Operating profit NOK −2,000
Equity NOK 25,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

BIINNTEKT AS is registered as a limited company in Kongsberg, Buskerud with organisation number 922809267. The business is classified under raising of animals n.e.c. (NACE 01.489). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Drift av bigårder og produksjon og salg av honning og bivoks, samt kjøp og salg av bier og utstyr relatert til driften. Investering i næringsvirksomhet, herunder aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 15,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 15,000
Operating profit
NOK −2,000
Equity
NOK 25,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns BIINNTEKT AS?

GEIR HANSSEN
BIINNTEKT AS
NOK 15,000 rev. · NOK −2,000 profit

BIINNTEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIINNTEKT AS

Who owns BIINNTEKT AS?

GEIR HANSSEN is the largest registered owner, with 100.0%.

What is the revenue of BIINNTEKT AS?

BIINNTEKT AS had revenue of NOK 15,000 in 2025.

Who is the general manager of BIINNTEKT AS?

Geir Hanssen is registered as general manager of BIINNTEKT AS.

Where is BIINNTEKT AS based?

BIINNTEKT AS has its business address in Kongsberg.

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.